WebSphere Application Server messages
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


SESN

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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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().
Action 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().
Action 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().
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action Drop the sessions table manually and restart the server.
SESN0050E: BackedHashtable:dropTable: Exception dropping sessions table - you should 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 - you should 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action 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.
Action None.
SESN0126I: {0} service has initialized successfully.
Explanation The z/OS Controller Service for HttpSession support in DRS has initialized successfully.
Action None.
SESN0127E: Method {0} caught exception: {1}
Explanation An exception was caught in the specified method.
Action None.
SESN0128E: Method {0} ERROR creating DRSControllerProxy: caught exception {1}
Explanation The specified method caught an exception while creating the DRSControllerProxy.
Action None.
SESN0129E: Method {0} ERROR creating DRSControllerProxy reference: caught exception {1}
Explanation The specified method caught an exception while creating the DRSControllerProxy reference.
Action None.
SESN0130E: Method {0} joinHAGroup returned null
Explanation In the specified method the call to joinHAGroup returned null.
Action None.
SESN0131E: Method {0} caught exception while creating callback: {1}
Explanation The specified method caught an exception while creating a callback.
Action None.
SESN0132E: Method {0} passed parameter entryKey = null: Attempt to create entry is aborted.
Explanation The specified method was passed a null entryKey parameter. The attempt to create entry is aborted.
Action None.
SESN0133E: Method {0} passed parameter value = null: Attempt to create entry is aborted.
Explanation The specified method was passed a null value for the value parameter. The attempt to create entry is aborted.
Action None.
SESN0134E: Method {0} Error creating DRS Instance in the Control Region : caught remote exception: {1}
Explanation The specified method caught a remote exception while creating the DRS Instance in the Control Region.
Action None.
SESN0135E: Method {0} Error creating DRS Instance in the Control Region : caught exception: {1}
Explanation The specified method caught an exception while creating the DRS Instance in the Control Region.
Action None.
SESN0136E: Method {0} Error creating SessionContext Group Instance in the Control Region : caught exception: {1}
Explanation The specified method caught an exception while creating the SessionContext Group Instance in the Control Region.
Action None.
SESN0137E: Method {0} DRSBootstrapMsg parameter = null.
Explanation The specified method was passed a null value for the DRSBootstrapMsg parameter.
Action None.
SESN0138E: Method {0} event parameter = null.
Explanation The specified method was passed a null value for the event parameter.
Action None.
SESN0139E: Method {0} cannot acquire proxy for token {1}.
Explanation The specified method was unable to acquire a proxy for the specified token.
Action None.
SESN0140E: Method {0} cannot convert token to byte array: token = {1}.
Explanation The specified method cannot convert the token to a byte array.
Action None.
SESN0141E: Method {0} cannot convert event {1} to byte array.
Explanation The specified method cannot convert the event to a byte array.
Action None.
SESN0142I: HttpSessDRSControllerVars DRS Instance {0} received event REPLICATION_UP.
Explanation The specified HttpSessDRSControllerVars DRS Instance received event REPLICATION_UP.
Action None.
SESN0143I: HttpSessDRSControllerVars DRS Instance {0} received event REPLICATION_DOWN.
Explanation The specified HttpSessDRSControllerVars DRS Instance received event REPLICATION_DOWN.
Action None.
SESN0144I: HttpSessDRSControllerVars DRS Instance {0} received event IS_CONGESTED.
Explanation The specified HttpSessDRSControllerVars DRS Instance received event IS_CONGESTED.
Action None.
SESN0145I: HttpSessDRSControllerVars DRS Instance {0} received event NOT_CONGESTED.
Explanation The specified HttpSessDRSControllerVars DRS Instance received event NOT_CONGESTED.
Action None.
SESN0146E: Method {0}: entryKey converted to a string key is null.
Explanation In the specified method, the string key converted from the entryKey is null.
Action None.
SESN0147E: Method {0} Error: Servant with token {1} is registered but appears in the unregistered table.
Explanation The servant is registered, but the token appears in the unregistered table.
Action None.
SESN0148E: Method {0} Error: Servant with token {1} is registered but does not appear in the registered table.
Explanation The servant is registered, but the token does not appear in the registered table.
Action None.
SESN0149E: Method {0} Error: Servant with token {1} is unregistered but appears in the registered table.
Explanation The servant is unregistered, but the token appears in the registered table.
Action None.
SESN0150E: Method {0} Error: context returned for instance {1} is null.
Explanation The context returned on lookup for the instance is null.
Action None.
SESN0151E: Method {0}: token parameter = null.
Explanation The specified method was passed a null value for the token parameter.
Action None.
SESN0152E: Method {0} Error: attempt to add token that already exists.
Explanation The specified method was passed a token to add that already exists.
Action None.
SESN0153E: Method {0} Error: Expected token {1} does not match tmp2 {2}.
Explanation The specified token does not match the token in tmp2.
Action None.
SESN0154E: Method {0} Error: Returned byte array could not be converted to an object.
Explanation The returned byte array could not be converted to an object..
Action None.
SESN0155E: Method {0} Error: Returned byte array is null.
Explanation The returned byte array is null.
Action None.
SESN0156E: Method {0} cannot create proxy for token {1}.
Explanation The specified method was unable to create a proxy for the specified token.
Action None.
SESN0157E: Method {0} Error: Method was called in incorrect environment.
Explanation The specified method was called in a non-control region environment.
Action None.
SESN0158E: Method {0} Error: context is null for stoken = {1} and id = {2}.
Explanation The context is null for the specified stoken and id.
Action None.
SESN0159E: Method {0} Error: cannot get unregistered entry for stoken {1}.
Explanation Unable to get an unregistered entry for the stoken.
Action None.
SESN0160E: Method {0} Error: cannot locate unregistered entry for stoken {1}.
Explanation Unable to locate an unregistered entry for the stoken.
Action None.
SESN0161E: Method {0}: GroupName parameter is null.
Explanation The specified method was passed a null value for the GroupName parameter.
Action None.
SESN0162E: Method {0}: token = null: failed to create control region instance.
Explanation The specified method failed to create the control region instance.
Action None.
SESN0163E: Method {0} Error: registerServant returned null.
Explanation The call to registerServant returned null.
Action None.
SESN0164E: Method {0} Error: stoken {1} does not match stokenTest {2}.
Explanation The specified stoken does not match the stokenTest token.
Action None.
SESN0165E: Method {0} Error: token {1} is not in the token array.
Explanation The specified stoken is not in the token array.
Action None.
SESN0166E: Method {0} instanceOffset error in the token table: token = {1}, instanceOffset is not >= 0.
Explanation The specified method encountered an instanceOffset error while processing the token.
Action None.
SESN0167E: Method {0} Error: confirmServantRegistration returned null.
Explanation The call to confirmServantRegistration returned null.
Action None.
SESN0168E: Method {0} Error: value parameter converted to session is null.
Explanation In the specified method, the session converted from the value parameter is null.
Action None.
Reference topic    

Terms of Use | Feedback

Last updated: Feb 21, 2008 7:07:28 AM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.servlet.resources.personalization.html

© Copyright IBM Corporation 2006, 2007. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)