Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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 |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | SESN0014E: DatabaseSessionContext:initalizeParameters - problem accessing configuration parameters. |
User response | Check/Correct Session Manager configuration values relating to database and restart the server. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | SESN0020E: checkMinimumInvalidationError encountered a problem checking minimum Invalidation time. |
User response | Restart the server. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | 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. |
Problem | Even when crossover detection is enabled, session accesses and references on user-spawned threads cannot be checked. |
User response | None. |
Problem | The z/OS Controller Service for HttpSession support in DRS has initialized successfully. |
User response | None. |
Problem | An exception was caught in the specified method. |
User response | None. |
Problem | The specified method caught an exception while creating the DRSControllerProxy. |
User response | None. |
Problem | The specified method caught an exception while creating the DRSControllerProxy reference. |
User response | None. |
Problem | In the specified method the call to joinHAGroup returned null. |
User response | None. |
Problem | The specified method caught an exception while creating a callback. |
User response | None. |
Problem | The specified method was passed a null entryKey parameter. The attempt to create entry is aborted. |
User response | None. |
Problem | The specified method was passed a null value for the value parameter. The attempt to create entry is aborted. |
User response | None. |
Problem | The specified method caught a remote exception while creating the DRS Instance in the Control Region. |
User response | None. |
Problem | The specified method caught an exception while creating the DRS Instance in the Control Region. |
User response | None. |
Problem | The specified method caught an exception while creating the SessionContext Group Instance in the Control Region. |
User response | None. |
Problem | The specified method was passed a null value for the DRSBootstrapMsg parameter. |
User response | None. |
Problem | The specified method was passed a null value for the event parameter. |
User response | None. |
Problem | The specified method was unable to acquire a proxy for the specified token. |
User response | None. |
Problem | The specified method cannot convert the token to a byte array. |
User response | None. |
Problem | The specified method cannot convert the event to a byte array. |
User response | None. |
Problem | The specified HttpSessDRSControllerVars DRS Instance received event REPLICATION_UP. |
User response | None. |
Problem | The specified HttpSessDRSControllerVars DRS Instance received event REPLICATION_DOWN. |
User response | None. |
Problem | The specified HttpSessDRSControllerVars DRS Instance received event IS_CONGESTED. |
User response | None. |
Problem | The specified HttpSessDRSControllerVars DRS Instance received event NOT_CONGESTED. |
User response | None. |
Problem | In the specified method, the string key converted from the entryKey is null. |
User response | None. |
Problem | The servant is registered, but the token appears in the unregistered table. |
User response | None. |
Problem | The servant is registered, but the token does not appear in the registered table. |
User response | None. |
Problem | The servant is unregistered, but the token appears in the registered table. |
User response | None. |
Problem | The context returned on lookup for the instance is null. |
User response | None. |
Problem | The specified method was passed a null value for the token parameter. |
User response | None. |
Problem | The specified method was passed a token to add that already exists. |
User response | None. |
Problem | The specified token does not match the token in tmp2. |
User response | None. |
Problem | The returned byte array could not be converted to an object.. |
User response | None. |
Problem | The returned byte array is null. |
User response | None. |
Problem | The specified method was unable to create a proxy for the specified token. |
User response | None. |
Problem | The specified method was called in a non-control region environment. |
User response | None. |
Problem | The context is null for the specified stoken and id. |
User response | None. |
Problem | Unable to get an unregistered entry for the stoken. |
User response | None. |
Problem | Unable to locate an unregistered entry for the stoken. |
User response | None. |
Problem | The specified method was passed a null value for the GroupName parameter. |
User response | None. |
Problem | The specified method failed to create the control region instance. |
User response | None. |
Problem | The call to registerServant returned null. |
User response | None. |
Problem | The specified stoken does not match the stokenTest token. |
User response | None. |
Problem | The specified stoken is not in the token array. |
User response | None. |
Problem | The specified method encountered an instanceOffset error while processing the token. |
User response | None. |
Problem | The call to confirmServantRegistration returned null. |
User response | None. |
Problem | In the specified method, the session converted from the value parameter is null. |
User response | None. |
Problem | Session Manager will use the specified property and value to control behavior. |
User response | Verify that the specified property and value will result in the desired behavior. |
Problem | Session Manager expected the specified property to contain a numeric value. The property will be ignored. |
User response | Correct the specified property value to make it a valid number. |
Problem | Session Manager expected the specified property to have a value within a certain range. Session Manager will use the closest valid value. |
User response | Correct the specified property value to make it within the documented range. |