|
Session and User Profiles messages |
|
SESN0001E: SessionContext:couldn't stop invalidation thread. Failed to stop session invalidation thread when reading updated configuration values. Latest configuration values involving invalidation may not be in use. Restart the server in order to pick up the latest values.
Explanation:
SESN0001E: SessionContext:couldn't stop invalidation thread. Failed to stop session invalidation thread when reading updated configuration values. Latest configuration values involving invalidation may not be in use.
User Response:
Restart the server in order to pick up the latest values.
SESN0002E: SessionContext:got unknown host exception. Failed to determine the host internet address.
Explanation:
SESN0002E: SessionContext:got unknown host exception. Failed to determine the host internet address.
User Response:
Restart the server. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
SESN0003E: SessionContext:the invalidation thread was interrupted by the JVM. Restart the server.
Explanation:
SESN0003E: SessionContext:the invalidation thread was interrupted by the JVM.
User Response:
Restart the server. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided
SESN0004E: SessionContext: an exception occurred while running the invalidator thread. Restart server.
Explanation:
SESN0004E: SessionContext: an exception occurred while running the invalidator thread.
User Response:
Restart server. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
SESN0005E: SessionContext: error with configuration parameters. Check/Correct Session Manager configuration values and restart the server.
Explanation:
SESN0005E: SessionContext: error with configuration parameters.
User Response:
Check/Correct Session Manager configuration values and restart the server.
SESN0006E: SessionContext: attempted to create a session while WebSphere Session Manager was stopped. This could occur when a Session request is received while Session Manager is stopped or reading in new configuration values. Start the Session Manager.
Explanation:
SESN0006E: SessionContext: attempted to create a session while WebSphere Session Manager was stopped. This could occur when a Session request is received while Session Manager is stopped or reading in new configuration values.
User Response:
Start the Session Manager.
SESN0007E: SessionContext: attempted to access a session while WebSphere Session Manager was stopped. This could occur when a Session request is received while Session Manager is stopped or reading in new configuration values. Start the Session Manager.
Explanation:
SESN0007E: SessionContext: attempted to access a session while WebSphere Session Manager was stopped. This could occur when a Session request is received while Session Manager is stopped or reading in new configuration values.
User Response:
Start the Session Manager.
SESN0008E: SessionContext: a user authenticated as {0} has attempted to access a session owned by {1} An attempt was made to access a session by an unauthenticated user or a different authenticated name. If Integrate WebSphere Security is enabled in the Session Manager then all requests that are part of the same session must share a common authentication identity.
Explanation:
SESN0008E: SessionContext: a user authenticated as {0} has attempted to access a session owned by {1} An attempt was made to access a session by an unauthenticated user or a different authenticated name. If Integrate WebSphere Security is enabled in the Session Manager then all requests that are part of the same session must share a common authentication identity.
User Response:
See the Infocenter for details on SessionManager Security Integration with HttpSession.
SESN0009E: SessionContext: unable to load IBM JCE, will use default id generator. The IBM JCE random session id generator encountered an error. Check if file WAS_ROOT/java/jre/lib/security/java.security has com.ibm.crypto.provider.IBMJCE as a security provider. If not, add the entry security.provider.2=com.ibm.crypto.provider.IBMJCE
Explanation:
SESN0009E: SessionContext: unable to load IBM JCE, will use default id generator. The IBM JCE random session id generator encountered an error.
User Response:
Check if file WAS_ROOT/java/jre/lib/security/java.security has com.ibm.crypto.provider.IBMJCE as a security provider. If not, add the entry security.provider.2=com.ibm.crypto.provider.IBMJCE
SESN0010E: BackedHashtableMR: Exception getting properties of the session. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0010E: BackedHashtableMR: Exception getting properties of the session.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0011E: SessionContext: setSessionTimeoutInfo Error. An exception was encountered while processing the session invalidation timeout values. Assure that the invalidation time specified in the Session Manager configuration and the session timeout value configured in the web application are correct and restart the server.
Explanation:
SESN0011E: SessionContext: setSessionTimeoutInfo Error. An exception was encountered while processing the session invalidation timeout values.
User Response:
Ensure that the invalidation time specified in the Session Manager configuration and the session timeout value configured in the web application are correct and restart the server.
SESN0012E: SessionData:putValue - null key entered. The HttpSession.putValue or HttpSession.setAttribute method was called from a servlet/JSP with a null key. Fix the servlet/JSP.
Explanation:
SESN0012E: SessionData:putValue - null key entered. The HttpSession.putValue or HttpSession.setAttribute method was called from a servlet/JSP with a null key.
User Response:
Fix the servlet/JSP.
SESN0013E: SessionData:putValue - null value entered for key {0}. The HttpSession.putValue or HttpSession.setAttribute method was called from a servlet/JSP with a null value. Fix the servlet/JSP.
Explanation:
SESN0013E: SessionData:putValue - null value entered for key {0}. The HttpSession.putValue or HttpSession.setAttribute method was called from a servlet/JSP with a null value.
User Response:
Fix the servlet/JSP.
SESN0014E: DatabaseSessionContext:initalizeParameters - problem accessing configuration parameters. Check/Correct Session Manager configuration values relating to database and restart the server.
Explanation:
SESN0014E: DatabaseSessionContext:initalizeParameters - problem accessing configuration parameters.
User Response:
Check/Correct Session Manager configuration values relating to database and restart the server.
SESN0015E: DatabaseSessionContext:processInvalidList - problem invalidating session. The database invalidation of timed out sessions has encountered an error. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0015E: DatabaseSessionContext:processInvalidList - problem invalidating session. The database invalidation of timed out sessions has encountered an error.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0016E: DatabaseSessionContext:performInvalidation detected an error. The database invalidation of timed out sessions has encountered an error. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0016E: DatabaseSessionContext:performInvalidation detected an error. The database invalidation of timed out sessions has encountered an error.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0017E: DatabaseSessionContext:couldn't stop PropertyWriter thread. Failed to stop Time Based Writer thread when reading updated configuration values. Latest configuration values may not be in use. Restart the server in order to pick up the latest values.
Explanation:
SESN0017E: DatabaseSessionContext:couldn't stop PropertyWriter thread. Failed to stop Time Based Writer thread when reading updated configuration values. Latest configuration values may not be in use.
User Response:
Restart the server in order to pick up the latest values.
SESN0018E: DatabaseSessionContext:the PropertyWriter thread was interrupted by the JVM. Restart the server.
Explanation:
SESN0018E: DatabaseSessionContext:the PropertyWriter thread was interrupted by the JVM.
User Response:
Restart the server.
SESN0019E: checkMinimumInvalidationError detected that TimeBaseWrite invalidation time was not at least 3 times the Write Interval. This was temporarily corrected. Update the Session Manager configuration values such that the Invalidation time is at least 3 times the Time Based Write Interval. Note that the invalidation time is also configured as Session Timeout in the Web Application definition.
Explanation:
SESN0019E: checkMinimumInvalidationError detected that TimeBaseWrite invalidation time was not at least 3 times the Write Interval. This was temporarily corrected.
User Response:
Update the Session Manager configuration values such that the Invalidation time is at least 3 times the Time Based Write Interval. Note that the invalidation time is also configured as Session Timeout in the Web Application definition.
SESN0020E: checkMinimumInvalidationError encountered a problem checking minimum Invalidation time. Restart the server.
Explanation:
SESN0020E: checkMinimumInvalidationError encountered a problem checking minimum Invalidation time.
User Response:
Restart the server.
SESN0021E: DatabaseSessionContext: an exception occurred while running the PropertyWriter thread. Restart server.
Explanation:
SESN0021E: DatabaseSessionContext: an exception occurred while running the PropertyWriter thread.
User Response:
Restart the server. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
SESN0022E: DatabaseSessionData: a problem occurred reading the creation time field from the database. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0022E: DatabaseSessionData: a problem occurred reading the creation time field from the database.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0023E: DatabaseSessionData: a problem occurred reading the maximum inactive interval field from the database. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0023E: DatabaseSessionData: a problem occurred reading the maximum inactive interval field from the database.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0024E: DatabaseSessionData: a problem occurred reading the application name field from the database. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0024E: DatabaseSessionData: a problem occurred reading the application name field from the database.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0025E: DatabaseSessionData: a problem occurred reading the user name field from the database. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0025E: DatabaseSessionData: a problem occurred reading the user name field from the database.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0026E: DatabaseSessionData: a problem occurred processing HttpSessionBindingListeners stored in the database. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0026E: DatabaseSessionData: a problem occurred processing HttpSessionBindingListeners stored in the database.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0027E: DatabaseSessionData: a problem occurred reading the listener count field from the database. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0027E: DatabaseSessionData: a problem occurred reading the listener count field from the database.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0028E: DatabaseSessionData.convertObject: Encountered an exception getting an EJB Object using the EJB Handle. The EJBObject was previously put to the session. A RemoteException was encountered while issuing getEJBObject() from Handle. Refer to EJB documentation.
Explanation:
SESN0028E: DatabaseSessionData.convertObject: Encountered an exception getting an EJB Object using the EJB Handle. The EJBObject was previously put to the session. A RemoteException was encountered while issuing getEJBObject() from Handle.
User Response:
Refer to EJB documentation.
SESN0029E: DatabaseSessionData.convertObject: Encountered an exception getting an EJB Home using the EJB Home Handle. The EJBHome was previously put to the session. A RemoteException was encountered while issuing getEJBHome() from Handle. Refer to EJB documentation.
Explanation:
SESN0029E: DatabaseSessionData.convertObject: Encountered an exception getting an EJB Home using the EJB Home Handle. The EJBHome was previously put to the session. A RemoteException was encountered while issuing getEJBHome() from Handle.
User Response:
Refer to EJB documentation.
SESN0030E: DatabaseSessionData.convertObject: Encountered an exception getting at Initial Context. An InitialContext was previously put to the session. A NamingException was encountered while reconstructing javax.naming.InitialContext(). Refer to naming server documentation for the error message.
Explanation:
SESN0030E: DatabaseSessionData.convertObject: Encountered an exception getting at Initial Context. An InitialContext was previously put to the session. A NamingException was encountered while reconstructing javax.naming.InitialContext().
User Response:
Refer to naming server documentation for the error message.
SESN0031E: DatabaseSessionData.putValueGuts: Encountered an exception getting EJB Home. An EJBHome was put to the session. A RemoteException occurred while issuing getHomeHandle(). Refer to EJB documentation.
Explanation:
SESN0031E: DatabaseSessionData.putValueGuts: Encountered an exception getting EJB Home. An EJBHome was put to the session. A RemoteException occurred while issuing getHomeHandle().
User Response:
Refer to EJB documentation.
SESN0032E: DatabaseSessionData.putValueGuts: Encountered an exception getting EJB Handle. An EJBObject was put to the session. A RemoteException occurred while issuing getHandle(). Refer to EJB documentation.
Explanation:
SESN0032E: DatabaseSessionData.putValueGuts: Encountered an exception getting EJB Handle. An EJBObject was put to the session. A RemoteException occurred while issuing getHandle().
User Response:
Refer to EJB documentation.
SESN0033E: DatabaseSessionData.putValueGuts: A javax.naming.Context was put to the session and a RemoteException occurred while issuing getEnvironment()on javax.naming.Context. Refer to naming server documentation for the error message.
Explanation:
SESN0033E: DatabaseSessionData.putValueGuts: A javax.naming.Context was put to the session and a RemoteException occurred while issuing getEnvironment()on javax.naming.Context.
User Response:
Refer to naming server documentation for the error message.
SESN0034E: DatabaseSessionData.getSwappableListeners: class not found. An attempt to deserialize a session object from the database has resulted in a ClassNotFoundException. The object to be deserialized must be contained in the classpath for all JVMs that can access the session.
Explanation:
SESN0034E: DatabaseSessionData.getSwappableListeners: class not found. An attempt to deserialize a session object from the database has resulted in a ClassNotFoundException. The object to be deserialized must be contained in the classpath for all JVMs that can access the session.
User Response:
Update the classpath so that attribute deserialized is in the classpath of the application.
SESN0035E: BackedHashtable:removeSessions - database error. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0035E: BackedHashtable:removeSessions - database error.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0036E: BackedHashtable:doInvalidations - database error. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0036E: BackedHashtable:doInvalidations - database error.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0037E: BackedHashtable:pollForInvalids - database error. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0037E: BackedHashtable:pollForInvalids - database error.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0038E: BackedHashtable:getConnection - database error. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0038E: BackedHashtable:getConnection - database error.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0039E: BackedHashtable:selectAndLock - database error. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0039E: BackedHashtable:selectAndLock - database error.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0040E: BackedHashtable:commonSetup - problem streaming object. Exception caught while trying to serialize session data for subsequent database write. The session data may be too large to serialize. Either put less data in the session or consider configuring Session Manager for MultiRow database mode.
Explanation:
SESN0040E: BackedHashtable:commonSetup - problem streaming object. Exception caught while trying to serialize session data for subsequent database write. The session data may be too large to serialize.
User Response:
Either put less data in the session or consider configuring Session Manager for MultiRow database mode.
SESN0041E: BackedHashtable:ejbStore - database error for session. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0041E: BackedHashtable:ejbStore - database error for session.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0042E: BackedHashtable:ejbCreate - database error. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0042E: BackedHashtable:ejbCreate - database error.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0043E: BackedHashtable: problem obtaining the configured datasource. Ensure that you have properly configured a datasource. When Session Manager persistence is enabled the Session Manager configuration must contain a valid datasource.
Explanation:
SESN0043E: BackedHashtable: problem obtaining the configured datasource.
User Response:
Ensure that you have properly configured a datasource. When Session Manager persistence is enabled the Session Manager configuration must contain a valid datasource.
SESN0044E: BackedHashtable: problem occurred reading in a single object of the application data for a session from the database. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0044E: BackedHashtable: problem occurred reading in a single object of the application data for a session from the database.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0045E: BackedHashtable: problem sending asynchronous last access updates to the database. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0045E: BackedHashtable: problem sending asynchronous last access updates to the database.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0046E: BackedHashtable: a database error occurred trying to clean up sessions after a web application reload. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0046E: BackedHashtable: a database error occurred trying to clean up sessions after a web application reload.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0047E: BackedHashtable:initConnPool - problem creating a table for sessions. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0047E: BackedHashtable:initConnPool - problem creating a table for sessions.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0048E: BackedHashtable:createTable - SQL Exception during CreateTable. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0048E: BackedHashtable:createTable - SQL Exception during CreateTable.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0049E: BackedHashtable:dropTable - Dropping old sessions table. The Session Manager has detected that the Sessions table was in an out-of-date format. The old table has been dropped and a new table will be created.
Explanation:
SESN0049E: BackedHashtable:dropTable - Dropping old sessions table. The Session Manager has detected that the Sessions table was in an out-of-date format. The old table has been dropped and a new table will be created.
User Response:
Drop the sessions table manually and restart the server.
SESN0050E: BackedHashtable:dropTable: Exception dropping sessions table - drop the sessions table manually. The Session Manager has detected that the Sessions table was in an out-of-date format. The old table could not be dropped automatically. The user should manually drop the sessions table and restart the server.
Explanation:
SESN0050E: BackedHashtable:dropTable: Exception dropping sessions table - drop the sessions table manually. The Session Manager has detected that the Sessions table was in an out-of-date format. The old table could not be dropped automatically.
User Response:
The user should manually drop the sessions table and restart the server.
SESN0051E: BackedHashtable:getValue - class not found. An attempt to deserialize a session object from the database has resulted in a ClassNotFoundException. The object to be deserialized must be contained in the classpath for all JVMs that can access the session.
Explanation:
SESN0051E: BackedHashtable:getValue - class not found. An attempt to deserialize a session object from the database has resulted in a ClassNotFoundException. The object to be deserialized must be contained in the classpath for all JVMs that can access the session.
User Response:
Update the classpath so that attribute deserialized is in the classpath of the application.
SESN0052E: BackedHashtable.getSession - error updating last acc time. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0052E: BackedHashtable.getSession - error updating last acc time.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0053E: BackedHashtable.checkValidity - error checking session validity. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0053E: BackedHashtable.checkValidity - error checking session validity.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0054E: BackedHashtable.removeNonCachedSessionError - error removing Cached session. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0054E: BackedHashtable.removeNonCachedSessionError - error removing Cached session.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0055E: BackedHashtable:handlePropertyHits - An attempt was made to write more than 2M to large column. The session data may be too large for the database column. Either put less data in the session or consider configuring Session Manager for MultiRow database mode.
Explanation:
SESN0055E: BackedHashtable:handlePropertyHits - An attempt was made to write more than 2M to large column. The session data may be too large for the database column.
User Response:
Either put less data in the session or consider configuring Session Manager for MultiRow database mode.
SESN0056E: BackedHashtable.oracleGetValue - error encountered. An exception was encountered when the getValue()/getAttribute() method was called to read the value from the database. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0056E: BackedHashtable.oracleGetValue - error encountered. An exception was encountered when the getValue()/getAttribute() method was called to read the value from the database.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0057E: BackedHashtableMR: a problem storing application data changes to the database. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0057E: BackedHashtableMR: a problem storing application data changes to the database.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0058E: BackedHashtableMR: a problem occurred inserting a new session into the database. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0058E: BackedHashtableMR: a problem occurred inserting a new session into the database.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0059E: SessionContextRegistry: a problem occurred processing a configuration from the session active object. Check/Correct Session Manager configuration values and restart the server.
Explanation:
SESN0059E: SessionContextRegistry: a problem occurred processing a configuration from the session active object.
User Response:
Check/Correct Session Manager configuration values and restart the server. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
SESN0060E: SessionContextRegistry: a problem occurred creating a session context. Check/Correct Session Manager configuration values and restart the server.
Explanation:
SESN0060E: SessionContextRegistry: a problem occurred creating a session context.
User Response:
Check/Correct Session Manager configuration values and restart the server. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
SESN0061E: SessionContextRegistry: a problem occurred creating the session PMI instrumentation. Check/Correct PMI configuration values and restart the server.
Explanation:
SESN0061E: SessionContextRegistry: a problem occurred creating the session PMI instrumentation.
User Response:
Check/Correct PMI configuration values and restart the server. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
SESN0062E: BackedHashtable.handleAsyncUpdates detected an exception. An exception has been detected while attempting to update the database with the session last access times. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0062E: BackedHashtable.handleAsyncUpdates detected an exception. An exception has been detected while attempting to update the database with the session last access times.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0063E: BackedHashtable.selectNoUpdateError - Exception in selectNoUpdate. If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
Explanation:
SESN0063E: BackedHashtable.selectNoUpdateError - Exception in selectNoUpdate.
User Response:
If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a datasource for Session Manager.
SESN0064E: SessionContextRegistry: getSessionContext is returning null. Check/Correct Session Manager configuration values and restart the server.
Explanation:
SESN0064E: SessionContextRegistry: getSessionContext is returning null.
User Response:
Check/Correct Session Manager configuration values and restart the server. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
SESN0065E: SessionContextRegistry: getSessionContext threw an exception. Check/Correct Session Manager configuration values and restart the server.
Explanation:
SESN0065E: SessionContextRegistry: getSessionContext threw an exception.
User Response:
Check/Correct Session Manager configuration values and restart the server. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
SESN0066E: Response is already commited to client. Session cookie cannot be set.
Explanation:
SESN0066E: Response is already commited to client so session cookie cannot be sent to client. Correct application to get at http session before writing anyhting to response.
User Response:
Response is already commited to client so session cookie cannot be sent to browser. Correct application to get at http session before writing anyhting to response.
SESN0100E: UPManagerBean - Error in finding by {0}. Error finding the user profile with given identity. The user profile you are querying may not have been created.
Explanation:
SESN0100E: UPManagerBean - Error in finding by {0}. Error finding the user profile with given identity. The user profile you are querying may not have been created.
User Response:
Create the user profile with given identity.
SESN0101E: UPManagerBean - Error in getting Read Only Bean Home. Error getting at read only enterprise bean home from naming server. Check whether read only enterprise bean is deployed correctly with the jndi name specified in xml file.
Explanation:
SESN0101E: UPManagerBean - Error in getting Read Only Bean Home. Error getting at read only enterprise bean home from naming server.
User Response:
Check whether read only enterprise bean is deployed correctly with the jndi name specified in xml file.
SESN0102E: UPManagerBean - Error in getting Read Write Bean Home. Error getting at read write enterprise bean home from naming server. Check whether read write enterprise bean is deployed correctly with the jndi name specified in xml file.
Explanation:
SESN0102E: UPManagerBean - Error in getting Read Write Bean Home. Error getting at read write enterprise bean home from naming server.
User Response:
Check whether read write enterprise bean is deployed correctly with the jndi name specified in xml file.
SESN0103E: UPManagerBean - error accessing IntialContext. Unable to get at InitialContext. Refer to naming server documentation for the error message. Correct and restart server.
Explanation:
SESN0103E: UPManagerBean - error accessing IntialContext. Unable to get at InitialContext.
User Response:
Refer to naming server documentation for the error message. Correct and restart server. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
SESN0104E: UserProfileManager - UserProfile not enabled. Userprofile is accessed while user profile is turned off. Enable the user profile in userprofile.xml located in properties folder.
Explanation:
SESN0104E: UserProfileManager - UserProfile not enabled. Userprofile is accessed while user profile is turned off.
User Response:
Enable the user profile in userprofile.xml located in properties folder.
SESN0105E: UserProfileManager - Error initializing specified classes. Server was unable to load the specified classes in xml file. Check whether classes specified in xml files are in application classpath.
Explanation:
SESN0105E: UserProfileManager - Error initializing specified classes. Server was unable to load the specified classes in xml file.
User Response:
Check whether classes specified in xml files are in application classpath.
SESN0106E: UserProfileManager - Error while initializing from Active Object. Error initializing the user profile manager. Check userprofile.xml in properties folder for any missing elements.
Explanation:
SESN0106E: UserProfileManager - Error while initializing from Active Object. Error initializing the user profile manager.
User Response:
Check userprofile.xml in properties folder for any missing elements.
SESN0107E: UserProfileManager - Error while getting properties from XML. Error initializing the user profile manager. Check userprofile.xml in properties folder for any missing elements.
Explanation:
SESN0107E: UserProfileManager - Error while getting properties from XML. Error initializing the user profile manager.
User Response:
Check userprofile.xml in properties folder for any missing elements.
SESN0108E: UserProfileManager - user {0} already exists. Unable to add user profile with given identity. Userprofile with given identity already exists.
Explanation:
SESN0108E: UserProfileManager - user {0} already exists. Unable to add user profile with given identity. Userprofile with given identity already exists.
User Response:
Use a different identity to create a profile for new user.
SESN0109E: UserProfileManager - error initializing DataWrapper class. Error initializing the datawrapper class specified in userprofile.xml file. Datawrapper class specified in xml file should be present in classpath.
Explanation:
SESN0109E: UserProfileManager - error initializing DataWrapper class. Error initializing the datawrapper class specified in userprofile.xml file. Datawrapper class specified in xml file should be present in classpath.
User Response:
Datawrapper class specified in xml file should be present in classpath.
SESN0110E: UserProfileManager - error while accessing Manager Bean. Error accessing user profile manager enterprise bean. Check whether user profile beans were properly deployed and started.
Explanation:
SESN0110E: UserProfileManager - error while accessing Manager Bean. Error accessing user profile manager enterprise bean.
User Response:
Check whether user profile beans were properly deployed and started.
SESN0111E: UserProfileManager - unable to find {0}. Error finding the user profile with given identity. The user profile you are querying may not have been created.
Explanation:
SESN0111E: UserProfileManager - unable to find {0}. Error finding the user profile with given identity. The user profile you are querying may not have been created.
User Response:
The user profile you are querying may not have been created, create the user profile first to successfully perform this operation.
SESN0112E: UserProfileManager - unable to find user profiles by {0}. Error accessing user profiles by given property. Check whether user profile beans were properly deployed and started.
Explanation:
SESN0112E: UserProfileManager - unable to find user profiles by {0}. Error accessing user profiles by given property.
User Response:
Check whether user profile beans were properly deployed and started.
SESN0113E: UserProfileManager - error removing user {0}. Error removing the specified user profile. The user profile you are trying to remove may not be present.
Explanation:
SESN0113E: UserProfileManager - error removing user {0}. Error removing the specified user profile. The user profile you are trying to remove may not be present.
User Response:
The user profile you are trying to remove may not have been created, create the user profile first to successfully perform this operation.
SESN0114E: UserProfileManager - error while getting new columns from extended class {0}. Unable to get at new columns from the extended datawrapper class. Datawrapper class specified in xml file should be present in classpath.
Explanation:
SESN0114E: UserProfileManager - error while getting new columns from extended class {0}. Unable to get at new columns from the extended datawrapper class. Datawrapper class specified in xml file should be present in classpath.
User Response:
Datawrapper class specified in xml file should be present in classpath
SESN0115E: UserProfile - error in user profile. Error occurred in user profile management. Check the logs for user profile exceptions.
Explanation:
SESN0115E: UserProfile - error in user profile. Error occurred in user profile management.
User Response:
Check the logs for user profile exceptions. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
SESN0116W: Session identifier {0} has exceeded the max length limit of {1}.
Explanation:
SESN0116W: Value specifed for the SessionIdentifierMaxLength property has been exceeded.
User Response:
Only set this property if absolutely necessary, and then set it to the largest value your installation can tolerate. If still experiencing this problem, it is likely due to repeated failovers. Investigate and fix the root cause of the failovers.
SESN0117I: Global sessions is enabled for Web modules running with the Web container-level session management configuration.
Explanation:
SESN0117I: Global sessions is enabled for Web modules running with the Web container-level session management configuration.
User Response:
If global sessions is not desired, disable global sessions.
SESN0118W: Time-based write is enabled with global sessions. Accessing a global session from more than one server or cluster may result in loss of session data integrity.
Explanation:
SESN0118W: The time-based write feature is enabled with global sessions. Unless all Web modules that access the session are in the same server or cluster, session data integrity may be lost.
User Response:
Disable the time-based write if Web modules that access global sessions are split across servers or clusters.
SESN0119W: Memory-to-memory replication is enabled with global sessions. Accessing a global session from more than one server or cluster may result in loss of session data integrity.
Explanation:
SESN0119W: The memory-to-memory replication feature is enabled with global sessions. Unless all Web modules that access the session are in the same server or cluster, session data integrity may be lost.
User Response:
Disable memory-to-memory replication if Web Modules that access global sessions are split across servers or clusters.
SESN0120I: Web module {0} will not participate in global sessions because the Web container-level session management configuration has been overridden.
Explanation:
SESN0120I: The specified Web module will not particpate in global sessions because the Web container-level session management configuration has been overridden either at the enterprise application- or Web module-level.
User Response:
If you want the Web module to participate in global sessions, disable the session management configuration that is specified at the enterprise application- or the Web module-level and restart the server.
SESN0121E: Session crossover detected in Web application {0}. Session {1} was retrieved when session {2} was expected - {3}
Explanation:
A call to request.getSession() returned a session other than the requested session.
User Response:
For information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
SESN0122E: Session crossover detected in Web application {0}. Session {1} was referenced by method {2} when session {3} was expected - {4}
Explanation:
An application referenced a session other than the session associated with the request.
User Response:
Check for possible application errors. For further information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
SESN0123E: Session crossover detected in Web application {0}. Session {1} was returned to the client when session {2} was expected - {3}
Explanation:
A cookie or url is being returned to the client containing a session id that is not associated with the request.
User Response:
For information on resolving this error, please consult the IBM WebSphere Application Server Support website available at: http://www-3.ibm.com/software/webservers/appserv/support.html. The site provides searchable databases of technotes, solutions, and e-fixes. Information on contacting the WebSphere Support team is also provided.
SESN0124W: Session crossover detection is enabled.
Explanation:
Checks for session crossover are being executed.
User Response:
For better performance, you may choose to disable these checks by setting the Webcontainer custom property DebugSessionCrossover=false.
SESN0125W: User-spawned thread accessing http session in Web application {0}. Session crossover checks cannot be made on user-spawned threads.
Explanation:
Even when crossover detection is enabled, session accesses and references on user-spawned threads cannot be checked.
User Response:
None.
Last updated:
Library | Support | Trademarks | Feedback