The HTTP Session1.0 catalog contains messages in the range BEA100000 - BEA100999. Messages in this catalog are part of the weblogic.servlet.internal.session Internationalization package and the weblogic.i18n Localization package.
BEA-100000
Error: ERROR: Invalid call to the deprecated method method!!
Description
The user code has invoked a method, which has been deprecated.
Cause
The method has been deprecated in the latest servlet specification.
Action
Check the specifcatoin for an alternative. If not corrected, you might see unpredictable behavior.
BEA-100001
Error: Unexpected error occurred while fetching all session IDs.
Description
The call failed with an exception.
Cause
An unexpected error occurred while fetching all session IDs when checking the session expiration.
Action
Check the exception for an exact error message.
BEA-100002
Error: Could not create new session using session ID: "sessionId"
Description
A new session creation call failed and received an exception.
Cause
This is an unexpected error.
Action
Check the exception for an exact error message.
BEA-100003
Info: Could not find session: "sessionId".
Description
This call was expected to return a session, but the session did not exist.
This is an informative message to convey that the session is being removed.
Action
If this was unexpected behavior, check the session timeout parameter.
BEA-100005
Error: Could not remove session: "sessionId".
Description
Session removal failed.
Cause
An unexpected error occurred while removing the session.
Action
Check the exception for the exact error message.
BEA-100006
Info: HTTP session file persistence: storing sessions in directory: directory.
Description
HTTP session file persistence: storing sessions in directory: directory. This is the directory to which HTTP sessions will be written.
Cause
This is an information only message.
Action
Make sure that the directory stores the sessions as per the PeristentStoreDir session parameter (weblogic.xml).
BEA-100007
Info: Erasing directory tree for persistent HTTP sessions: directory.
Description
Erasing directory tree for persistent HTTP sessions: directory - for file based persistent sessions. This will remove the directory tree from the disk.
Cause
The storage directory is being deleted as a result of session invalidation.
Action
Make sure that the deletion is happening while removing sessions.
BEA-100008
Error: Cannot delete "directory".
Description
Unable to delete file persistent store directory "directory".
Cause
Failed to delete the storage directory.
Action
Make sure the permissions on this directory are OK. Make sure the file/directory is not in use by another process.
BEA-100009
Info: Creating a new session with ID id.
Description
Creating a new session with ID id. This is a randomly created session ID.
Cause
This is an information only message.
Action
Make sure the session ID length is consistent with the IDLen session parameter in weblogic.xml.
BEA-100010
Debug: Session ID: id. Stored to: path.
Description
Session stored to persistent store.
Cause
The container persists the modified session onto the disk after the request is served.
Action
Make sure the path is consistent with the session parameter, PersistentStoreDir (weblogic.xml).
BEA-100011
Error: An error occurred while serializing session data. Deleting this session.
Description
Serialization of the session attributes failed.
Cause
This might be due to a change in the class definition or serialVerUID.
Action
Check the exception for the exact error message and take appropriate action.
BEA-100012
Debug: Invalidating session with Session ID:id.
Description
Invalidating session with Session ID:id.
Cause
This is an information only message indicating that the session is being invalidated.
Action
Make sure this was triggered by a normal session expiration or user code.
BEA-100013
Info: path Not invalidated. The session serialized into the file system does not exist.
Description
path Not invalidated. The session serialized into the file system does not exist.
Cause
Could not find the session. Does not exist.
Action
This session might have been deleted by a trigger in some other server, which is pointing to the same storage.
BEA-100014
Error: Cannot delete the HTTP session storage file: file
Description
Cannot delete the HTTP session storage file: file, which is used by file-based session persistence.
Cause
Unable to delete the file used for session storage.
Action
Make sure some other application does not have a lock on the file and that permissions are assigned appropriately.
BEA-100015
Info: Deleted file based session persistent store file: file.
Description
Deleted file based session persistent store file: file.
Cause
This is an informational message indicating that the storage file is being deleted.
Action
Make sure the deletion is consistent with the path defined in PersistentStoreDir (weblogic.xml)
This is an information message to log the statistics for session expiration.
Action
Make sure the total session count in the persistent store and number of expired session count look reasonable.
BEA-100028
Error: Could not deserialize session data.
Description
Could not deserialize session data.
Cause
Failed to deserialize session data.
Action
Make sure the object you are putting into the session is serializable and also the non-transient object it aggregates are also serializable. If any of the non-transient objects in the entire object graph are not serializable, you will receive this error message.
BEA-100029
Warning: A session containing non-serializable objects was reloaded. Discarding non-serializable objects.
Description
A session containing non-serializable objects was reloaded. Discarding non-serializable objects.
Cause
Data, which cannot be serialized, was discarded as the container cannot store that into the persistent store.
Action
If the data (which was discarded) was important, make it serializable.
BEA-100030
Info: HTTP session expired. Session ID sessionId.
Description
HTTP session expired. Session ID sessionId.
Cause
This is an informational message indicating that the session with ID sessionId has been expired.
Action
If the session expired sooner than expected, check the SessionTimeout parameter in weblogic.xml.
BEA-100031
Error: An error occurred while unregistering servlet session runtime MBean: desc.
Description
This runtime MBean is used to monitor statistics for the HTTP sessions.
Cause
Failed to remove this MBean.
Action
Check the exception for the exact error message.
BEA-100032
Error: An error occurred while creating a servlet session runtime MBean.
Description
This runtime MBean is used to monitor statistics for the HTTP sessions.
Cause
Failed to create this MBean.
Action
Check the exception for the exact error message.
BEA-100033
Error: The license for replicated sessions is invalid: desc. Downgrading sessions to memory (not replicated).
Description
The sessions will not be replicated to other servers in the cluster.
Cause
The license was not valid to support replicated sessions.
Action
Check your license. You might want to upgrade it to a clustering/replication license. Alternatively, you can use file/jdbc persistence for session store reliability.
BEA-100034
Info: Timer Checking for session expiration for ID: id Web application: path.
Description
Timer Checking for session expiration for ID: id Web application: path.
Cause
The trigger (which checks sessions for expiration periodically) was just fired.
Action
Check the InvalidationIntervalSecs parameter values in weblogic.xml.
BEA-100035
Info: Timer invalidated session ID: id Web application: path, because it expired.
Description
Timer invalidated session ID: id Web application: path, because it expired.
Cause
This message was logged by the Web application level timer, which checks the sessions for expiration periodically.
Action
If the session expired too soon, check SessionTimeout in weblogix.xml..
BEA-100037
Debug: Creating SessionContext of type: type for Web application: path.
Description
Creating SessionContext of type: type for Web application: path.
Cause
This message is logged on Web application deployment.
Action
Make sure the SessionContext type is consistent with PersistentStoreType (weblogic.xml).
BEA-100038
Error: Unknown persistent type: type for Web application: path. Valid types are: memory/file/replicated/jdbc/cookie/replicated_if_clustered.
Description
Unknown persistent type: type for Web application: path. Valid types are: memory/file/replicated/jdbc/cookie/replicated_if_clustered.
Cause
The persistent store type you specified for this Web application is not recognized.
Action
Check the PersistentStoreType parameter in weblogic.xml. The valid values are: memory/file/replicated/cookie/jdbc/replicated_if_clustered.
BEA-100039
Error: Replicated HTTP sessions specified for webapp: path, but clustering not enabled.
Description
Replicated HTTP sessions specified for webapp: path, but clustering not enabled.
Cause
The session replication mechanism relies on clustering, which has not been configured.
Action
Please setup clustering or change the PersistentStoreType in weblogic.xml to memory/file/jdbc/cookie
BEA-100040
Info: getAttribute(): name was a Handle, reconstructing the EJBObject
Description
getAttribute(): name was a Handle, reconstructing the EJBObject
Cause
This is an informational message indicating that the container is storing only the handle for the EJBObject placed into the session.
Action
No action required.
BEA-100041
Info: setAttribute(): name was an EJBObject. Storing the handle into the session.
Description
setAttribute(): name was an EJBObject. Storing the handle into the session.
Cause
The container found an EJB handle stored in the session. Will reconstruct the EJB object before returning.
Action
No action required.
BEA-100042
Error: An error occurred while reconstructing the EJBObject: name put into the session.
Description
An error occurred while reconstructing the EJBObject: name put into the session.
Cause
The container found an EJB handle stored in the session. However, it failed to reconstruct the EJBObject using that handle.
Action
Make sure the handle is still valid. Check the exception for the exact error message.
BEA-100043
Error: An error occurred while finding the handle for the EJBObject: name.
Description
An error occurred while finding the handle for the EJBObject: name.
Cause
The container stores only the handle for an EJBObject put into session. However, in this case, it failed to find the handle.
Action
Check the RemoteException for the exact error message details.
BEA-100044
Info: Found WLCookie cookie name=value.
Description
Found WLCookie cookie name=value.
Cause
The cookie persistence mechanism relies on setting the cookie header.
The cookie persistence mechanism relies on setting the cookie header.
Action
The cookie was found to be malformed. Only strings are supported for cookie-based persistence. Also make sure you do not have characters in the attributes name/values, which can break the cookie syntax.
BEA-100046
Info: Creating new session with ID: id for Web application: webapp.
Description
Creating new session with ID: id for Web application: webapp.
Cause
A new session has been created.
Action
Make sure the length is equal to the IDLen parameter in weblogic.xml.
BEA-100047
Info: Performing the database operation: op Id: id Web application: webapp.
Description
Performing the database operation: op Id: id Web application: webapp.
Cause
This is an informational message for JDBC-based persistence.
Action
No action required. Meant for debugging purposes only.
BEA-100048
Info: Looked up ROID: roid from host host:port for ID: id.
Description
Looked up ROID: roid from host host:port for ID: id.
Cause
The replicated session ID was not found in the current server. Perhaps this server is not the primary/secondary. Will try to retrieve the session from the assigned secondary if it is alive.
Action
No action required.
BEA-100049
Error: Error looking up session with id:id
Description
Error looking up session with id:id - session refresh failed
Cause
Got RemoteException looking up session from the secondary
Action
Check if the secondary server is down. Note that it is not recommended to kill both the primary and secondary server at the same time. Remember the replication happens lazily, upon request. So if you need to bring down the secondary server too give sufficient time so that the active end users hit their sessions and they get replicated.
BEA-100050
Info: The current server is becoming primary for replicated session ID: id.
Description
The current server is becoming primary for replicated session ID: id.
Cause
The current server is taking the role of primary for the given session.
Action
No action required.
BEA-100051
Info: The current server is becoming the secondary for replicated session ID: id.
Description
The current server is becoming the secondary for replicated session ID: id.
Cause
The current server is taking the role of primary for the given session.
Action
No action required.
BEA-100052
Info: Unregistering replicated session ID: id.
Description
Unregistering replicated session ID: id.
Cause
The current server is going to unregister the given session.
Action
The session was invalidated. No action required.
BEA-100053
Warning: Failed to update the secondary server for HTTP session ID: id.
Description
Failed to update the secondary server for HTTP session ID: id.
Cause
Failed to update the secondary server for the modification that occurred in the current request.
Action
Verify the secondary server is alive, and make sure the objects put into the session are all serializable. Also, check the exception for the exact error message.
BEA-100054
Warning: Failed to find the secondary server for HTTP session ID: id.
Description
Failed to find the secondary server for HTTP session ID: id.
Cause
Unable to find the secondary server for the replicated session.
Action
Verify the clustering is configured properly and there is more than one server in the cluster.
BEA-100055
Info: The generated session ID: id contains a reserved keyword. Regenerating.
Description
The generated session ID: id contains a reserved keyword. Regenerating.
Cause
On win32, if the session ID contains a reserved keyword, the file-based persistence fails. This is because it relies upon successful creation of subdirectories.
Action
No action required. The session ID will be regenerated. The reserved words are: "CON", "PRN", "AUX", "NUL" "COM1", "COM2", "COM3", "COM4", "COM5", "COM6", "COM7", "COM8", "COM9", "LPT1", "LPT2", "LPT3", "LPT4", "LPT5", "LPT6", "LPT7", "LPT8", "LPT9"}, "CLOCK$"
BEA-100056
Error: webapp: The session with ID: id was invalidated before the session creation and registration could complete.
Description
webapp: The session with ID: id was invalidated before the session creation and registration could complete.
Cause
This is a past-release problem.
Action
Contact BEA support and file a bug report.
BEA-100057
Error: This server does not have deployment for the Web application with context path: contextName. The callback: callback failed while replicating the session. Check your configuration; only uniform configurations in a cluster are supported.
Description
This server does not have deployment for the Web application with context path: contextName. The callback: callback failed while replicating the session. Check your configuration; only uniform configurations in a cluster are supported.
Cause
WebLogic clustering relies on uniform Web application deployment across the cluster. It seems the Web application was not deployed on all the servers.
Action
Redeploy the Web application, and make sure it targets the cluster/all members in the cluster.
BEA-100058
Error: PersistentStoreType for the Web application with context path: contextName is not replicated. The callback: callback failed while replicating the session. Check your configuration; only uniform configurations in a cluster are supported.
Description
PersistentStoreType for the Web application with context path: contextName is not replicated. The callback: callback failed while replicating the session. Check your configuration; only uniform configurations in a cluster are supported.
Cause
WebLogic Server clustering relies on uniform Web application deployment across the cluster. It seems the Web application was not deployed on all the servers with uniform configuration.
Action
Redeploy the Web application, and make sure it targets the cluster/all members in the cluster. Also the PersistentStore type should be set to "replicated" for all cluster members.
BEA-100059
Error: An unexpected error occurred while cleaning up sessions during undeployment of Web application: context.
Description
An unexpected error occurred while cleaning up sessions during undeployment of Web application: context.
Cause
The trigger failed to cleanup the expired session.
Action
Check the exception for the exact error message. When using JDBC-based HTTP session persistence, make sure the database is set up properly. For file-based persistence, make sure the permissions on the storage directory are appropriately set.
BEA-100060
Error: An unexpected error occurred while retrieving the session for Web application: logContext.
Description
An unexpected error occurred while retrieving the session for Web application: logContext.
Cause
Failed to retrieve the session from persistent store.
Action
Check your configuration, and check the exception for the exact error message. Also, check the WebLogic Server documentation for more details about how to configure session persistence for Web applications.
BEA-100061
Warning: Web application: logContext tried to place a non-serializable attribute: name into the session: id. This attribute will be lost upon redeployment. This message is logged only once per session.
Description
Web application: logContext tried to place a non-serializable attribute: name into the session: id. This attribute will be lost upon redeployment. This message is logged only once per session.
Cause
The session.setAttribute(name, value) was invoked with a non-serializable value for memory-based sessions.
Action
If you want the session data to survive redeployment, make sure all attributes are serializable. Otherwise, the non-serializable data will be lost upon redeployment.
BEA-100062
Warning: Web application: logContext tried to place a non-serializable attribute: name into the session: id. This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be replicated to the secondary server. This message is logged only once per session.
Description
Web application: logContext tried to place a non-serializable attribute: name into the session: id. This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be replicated to the secondary server. This message is logged only once per session.
Cause
The session.setAttribute(name, value) was invoked with a non-serializable value for a replicated session.
Action
If you want the session data to survive redeployment and session failovers, make sure all attributes are serializable. Otherwise, the non-serializable data will be lost upon failover/redeployment.
BEA-100063
Warning: Web application: logContext tried to place a non-serializable attribute: name into the session: id. This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the disk. This message is logged only once per session.
Description
Web application: logContext tried to place a non-serializable attribute: name into the session: id. This attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the disk. This message is logged only once per session.
Cause
The session.setAttribute(name, value) was invoked with a non-serializable value for a file-based persistent session.
Action
If you want the session data to survive redeployment and session failovers, make sure all the attributes are serializable. Otherwise, the non-serializable data will be lost upon failover/redeployment.
BEA-100064
Warning: Web application: logContext tried to place a non-serializable attribute: name into the session: id. The attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the database. This message is logged only once per session.
Description
Web application: logContext tried to place a non-serializable attribute: name into the session: id. The attribute will be lost upon redeployment or session failover. Also, such attributes will be scoped to the current server only and will not be persisted to the database. This message is logged only once per session.
Cause
The session.setAttribute(name, value) attribute was invoked with a non-serializable value for a JDBC-based persistent session.
Action
If you want the session data to survive redeployment and session failovers, make sure all the attributes are serializable. Otherwise, the non-serializable data will be lost upon failover/redeployment.
BEA-100065
Error: logContext. Failed to remove attributes for HTTP session ID: id.
Description
logContext. Failed to remove attributes for HTTP session ID: id.
Cause
An unexpected error occurred during HTTP session invalidation.
Action
Check the error message for the exact cause.
BEA-100066
Error: Failed to lookup the replicated session object for Web application: logContext, session ID: id.
Description
Failed to lookup the replicated session object for Web application: logContext, session ID: id.
Cause
The ReplicationManager returned the NotFoundException.
Action
This happens if the object has been cleaned up underneath or the version number does not match with the secondary object. This should not happen normally. Unwanted failovers at the front-end can cause unnecessary session failovers in the backend, which could result in this error in certain situations. Check the error for more information.
BEA-100067
Error: Failed to lookup the secondary information for Web application: logContext session ID: id.
Description
Failed to lookup the secondary information for Web application: logContext session ID: id.
Cause
The ReplicationManager returned the NotFoundException.
Action
This happens if the object has been cleaned up underneath or the version number does not match with the secondary object. This should not happen normally. Unwanted failovers at the front-end can cause unnecessary session failovers in the backend, which could result in this error in certain situations. Check the error for more information.
BEA-100068
Error: Failed to lookup the secondary information for Web application: logContext session ID: id.
Description
Failed to lookup the secondary information for Web application: logContext session ID: id.
Cause
The ReplicationManager failed to lookup the secondary information for a valid session.
Action
This is an unexpected error. Check the error message for details.
BEA-100069
Info: getAttribute(): name was a HomeHandle, reconstructing the EJBHome
Description
getAttribute(): name was a HomeHandle, reconstructing the EJBHome
Cause
This is an informational message indicating that the container is storing only the handle for the EJBHome placed into the session.
Action
No action required.
BEA-100070
Error: Error reconstructing the EJBHome put into session for name: name
Description
Error reconstructing the EJBHome put into session for name: name
Cause
The container found an EJBHome handle stored in the session. However, it failed to reconstruct the EJBHome using that EJBHome handle.
Action
Make sure the HomeHandle is still valid. Check the exception for the exact error message.
BEA-100071
Info: setAttribute(): name was an EJBHome, storing the HomeHandle into the session
Description
setAttribute(): name was an EJBHome, storing the HomeHandle into the session
Cause
The container found an EJBHome handle stored in the session. Will reconstruct the EJBHome object before returning.
Action
No action required.
BEA-100072
Error: Error in finding the homeHandle for the EJBHome: name
