Explanation | This error occurs when a session request is received while the server is stopping. |
Action | Restart the server. |
Explanation | This error occurs when a session request is received while the server is stopping. |
Action | Restart the server. |
Explanation | The Session Security Integration feature has detected an attempt to access a session by an unauthorized user. |
Action | No action is required. |
Explanation | The HttpSession.putValue or HttpSession.setAttribute method cannot be called with a null key. |
Action | Modify the servlet or JSP to pass a non-null key. |
Explanation | The HttpSession.putValue method cannot be called with a null value. |
Action | Modify the servlet or JSP to pass a non-null value. |
Explanation | An error occurred when invalidating a timed out database session. |
Action | If a SQLException has occurred, refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a data source the for Session Manager. |
Explanation | An error occurred when invalidating a timed out database 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 data source for the Session Manager. |
Explanation | When Time Based Writes are used, the session timeout must be at least 3 times the Write Interval. The session timeout was temporarily corrected. |
Action | Update the Session Manager configuration values so that the session timeout is at least 3 times the Time Based Write Interval. |
Explanation | An error occurred when processing HttpSessionBindingListeners stored in the database. |
Action | If a SQLException has occurred,refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a data source for the Session Manager. |
Explanation | An error occurred when getting an enterprise bean (EJB) object using the EJB handle. The EJBObject was previously added to the session. A RemoteException occured while issuing the getEJBObject method from the handle. |
Action | Refer to EJB documentation. |
Explanation | An error occured when getting an enterprise bean (EJB) Home using the EJB Home Handle. The EJBHome was previously added to the session. A RemoteException was encountered while issuing the getEJBHome method from Handle. |
Action | Refer to EJB documentation. |
Explanation | An error occurred when getting at the Initial Context. An InitialContext was previously added to the session. A NamingException was encountered while reconstructing the javax.naming.InitialContext method. |
Action | Refer to naming server documentation for the error message. |
Explanation | An error occurred when getting EJB Home. An EJBHome was added to the session. A RemoteException occurred while issuing the getHomeHandle method. |
Action | Refer to EJB documentation. |
Explanation | An error occurred when getting EJB Handle. An EJBObject was put to the session. A RemoteException occurred while issuing the getHandle method. |
Action | Refer to EJB documentation. |
Explanation | 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. |
Explanation | 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 class path for all JVMs that can access the session. |
Action | Update the class path so that attribute deserialized is in the class path of the application. |
Explanation | An error occurred when trying to remove 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 data source for the Session Manager. |
Explanation | An error occurred when trying to invalidate a session 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 data source for the Session Manager. |
Explanation | An error occurred when trying to poll the database for non valid 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 data source for the Session Manager. |
Explanation | An error occurred when trying to get a connection 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 data source for the Session Manager. |
Explanation | A database error has occurred. |
Action | If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a data source for the Session Manager. |
Explanation | The session data may be too large to serialize. |
Action | Either put less data in the session or consider configuring Session Manager for multi-row database mode. |
Explanation | An error occurred when trying to store a session 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 data source for the Session Manager. |
Explanation | An error occurred when trying to insert a 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 data source for the Session Manager. |
Explanation | An error occurred when trying to obtain the configured data source. |
Action | Ensure that you have properly configured a data source. When Session Manager persistence is enabled the Session Manager configuration must contain a valid data source. |
Explanation | An error occurred when trying to read in an 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 data source for theSession Manager. |
Explanation | An error occurred when trying to initialize 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 data source for the Session Manager. |
Explanation | An attempt to deserialize a session object from the backend has resulted in a ClassNotFoundException. The object to be deserialized must be contained in the class path for all JVMs that can access the session. |
Action | Update the class path so that attribute deserialized is in the class path of the application. |
Explanation | 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. |
Explanation | An exception was encountered when the getValue or 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 data source for the Session Manager. |
Explanation | An error occurred when 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 data source for the Session Manager. |
Explanation | 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 data source for the Session Manager. |
Explanation | An exception has been detected while attempting to access 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 data source for the Session Manager. |
Explanation | The response is already committed to client so the session cookie cannot be sent to client. |
Action | Modify the application to access the HTTP session before writing anything to the response. |
Explanation | The value specified for the SessionIdentifierMaxLength property has been exceeded. |
Action | Only set this property if absolutely necessary. If this property is required, set it to the largest value that 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. |
Explanation | This message is for informational purposes only. |
Action | If global sessions are not required, disable them by setting the Servlet21SessionCompatibility property to false. |
Explanation | If the time-based write feature is enabled with global sessions, and all the web modules that access the global session are not in the same server or cluster, session data integrity can be lost. |
Action | Disable the time-based write feature if web modules that access a global session are split across servers or clusters. |
Explanation | If memory-to-memory replication is enabled with global sessions, and all the web modules that access the global session are not in the same server or cluster, session data integrity can be lost. |
Action | Disable memory-to-memory replication if web modules that access a global session are split across servers or clusters. |
Explanation | The specified web module will not participate 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 web module level, then restart the server. |
Explanation | A call to the request.getSession method returned a session other than the requested session. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An application referenced a session other than the session associated with the request. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | A cookie or URL was returned to the client containing a session ID that is not associated with the request. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Checks for session crossover are being initiated. |
Action | For better performance, you can disable these checks by setting the web container custom property DebugSessionCrossover to false. |
Explanation | The z/OS Controller Service for HttpSession support in DRS has initialized successfully. |
Action | This message is for informational purposes only. |
Explanation | An exception was caught in the specified method. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method caught an exception while creating the DRSControllerProxy. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method caught an exception while creating the DRSControllerProxy reference. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | In the specified method the call to joinHAGroup returned null. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method caught an exception while creating a callback. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method was passed a null entryKey parameter. The attempt to create entry is aborted. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method was passed a null value for the value parameter. The attempt to create entry is aborted. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method caught a remote exception while creating the DRS Instance in the Control Region. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method caught an exception while creating the DRS Instance in the Control Region. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method caught an exception while creating the SessionContext Group Instance in the Control Region. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method was passed a null value for the DRSBootstrapMsg parameter. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method was passed a null value for the event parameter. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method was unable to acquire a proxy for the specified token. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method cannot convert the token to a byte array. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method cannot convert the event to a byte array. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified HttpSessDRSControllerVars DRS Instance received event REPLICATION_UP. |
Action | This message is for informational purposes only. |
Explanation | The specified HttpSessDRSControllerVars DRS Instance received event REPLICATION_DOWN. |
Action | This message is for informational purposes only. |
Explanation | The specified HttpSessDRSControllerVars DRS Instance received event IS_CONGESTED. |
Action | This message is for informational purposes only. |
Explanation | The specified HttpSessDRSControllerVars DRS Instance received event NOT_CONGESTED. |
Action | This message is for informational purposes only. |
Explanation | In the specified method, the string key converted from the entryKey is null. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The servant is registered, but the token appears in the unregistered table. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The servant is registered, but the token does not appear in the registered table. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The servant is unregistered, but the token appears in the registered table. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The context returned on lookup for the instance is null. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method was passed a null value for the token parameter. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method was passed a token to add that already exists. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified token does not match the token in tmp2. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The returned byte array could not be converted to an object. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The returned byte array is null. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method was unable to create a proxy for the specified token. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method was called in a non-control region environment. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The context is null for the specified stoken and id. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Unable to get an unregistered entry for the stoken. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Unable to locate an unregistered entry for the stoken. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method was passed a null value for the GroupName parameter. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method failed to create the control region instance. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The call to registerServant returned null. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified stoken does not match the stokenTest token. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified stoken is not in the token array. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified method encountered an instanceOffset error while processing the token. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The call to confirmServantRegistration returned null. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | In the specified method, the session converted from the value parameter is null. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The session manager uses the specified property and value to control behavior. |
Action | Verify that the specified property and value will result in the desired behavior. |
Explanation | The session manager expected the specified property to contain a numeric value. |
Action | Modify the specified property value to make it a valid number. |
Explanation | The session manager expected the specified property to have a value within a certain range. The session manager instead uses the closest valid value. |
Action | Correct the specified property value to make it within the documented range. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The session database table has been created incorrectly. |
Action | Drop the table manually. |
Explanation | An error occurred when attempting to start a Local Transaction. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An error occurred while cleaning up a Local Transaction causing it to be rolled back. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The session cannot be persisted right now because it is currenly being accessed by a servlet. It will be persisted on the next run of the Time Based Writer thread. |
Action | This message is for informational purposes only. |
Explanation | Got a null database connection. |
Action | If a SQLException has occurred then refer to the appropriate database documentation for your environment. Also, ensure that you have properly configured a data source for the Session Manager. |
Explanation | Unable to access the ComponentMetaDataAccessor. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified property is too large for the database. |
Action | Reduce the size of the property or do not store it in the session. |
Explanation | Specifies the mode for Memory To Memory replication for this app. |
Action | This message is for informational purposes only. |
Explanation | The Serialize Session Access feature is enabled and configured not to allow access on timeout. |
Action | Check for hung applications, possibly by dumping the threads of the application server. Consider either increasing the timout, or allowing session access on timeout. |
Explanation | Unable to access the CoreStack service and join the HAGroup. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An error occurred creating the session backing store on zOS. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Unable to establish zOS servant affinity for this session. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | Unable to release zOS servant affinity for this session. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The custom property can only be set at server level. |
Action | Remove the custom property from the application or module-level configuration. Change the server-level configuration if applicable. |
Explanation | This message is for informational purposes only. |
Action | No action is required. |
Explanation | The ID generator generated an ID that already exists. It therefore generates another ID. |
Action | No action is required. |
Explanation | Server id was not obtained from server.xml. |
Action | Correct the configuration if necessary. |
Explanation | An error occurred while getting the zOS server ID |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | This zOS base server will replicate session data for servant failover. |
Action | This message is for informational purposes only. |
Explanation | Object was not able to be serialized |
Action | Make sure object is serializable. |
Explanation | Attribute could not be serialized. |
Action | Make sure object is serializable. |
Explanation | Attribute could not be serialized |
Action | Make sure object is serializable. |
Explanation | A session attribute name cannot match the session ID in a database multi-row configuration. |
Action | Change the session attribute name in order to have the attribute persisted. |
Explanation | The Application Server cannot locate the defined replication domain. |
Action | Create the replication domain and restart the server or disable memory-to-memory session replication for all of the applications. |
Explanation | It appears that the session index in your table was created outside of the Application Server. |
Action | Drop the index and restart the Application Server. |
Explanation | The syntax of the specified httpSessionCache JCache configuration URI is invalid. |
Action | Correct the syntax of the specified httpSessionCache configuration URI. |
Explanation | An operation against the cache failed due to the specified exception. |
Action | See the exception for more details. The JCache provider's configuration might need to be updated. |
Explanation | An operation against the cache failed due to the specified exception. |
Action | See the exception for more details. The JCache provider's configuration might need to be updated. |
Explanation | An operation against the cache failed due to the specified exception. |
Action | See the exception for more details. The JCache provider's configuration might need to be updated. |
Explanation | An operation against the cache failed due to the specified exception. |
Action | See the exception for more details. The JCache provider's configuration might need to be updated. |
Explanation | An operation against the cache failed due to the specified exception. |
Action | See the exception for more details. The JCache provider's configuration might need to be updated. |
Explanation | An operation against the cache failed due to the specified exception. |
Action | See the exception for more details. The JCache provider's configuration might need to be updated. |
Explanation | An operation against the cache failed due to the specified exception. |
Action | See the exception for more details. The JCache provider's configuration might need to be updated. |
Explanation | The sessionCache feature was unable to fully initialize due to missing or invalid configuration. |
Action | Verify that the server configuration defines an httpSessionCache element that includes a libraryRef attribute. |
Explanation | The sessionCache feature could not find a JCache provider to load. |
Action | Verify that the library contains a JCache provider and all paths are specified correctly. |
Explanation | The Infinispan caches that are used for HTTP session persistence require additional configuration to persist sessions across servers. Liberty generates this configuration when it is not provided by the user. |
Action | No action is required if you are satisfied with the generated configuration. Otherwise, the generated configuration can be used as a starting point. |
Explanation | The specified configuration is ignored as it is provided by the specified cacheManagerRef. |
Action | No action is required. |
Explanation | The property CloneSeparator should be exactly one char and it cannot be space. |
Action | Modify the CloneSeparator custom property. |
Explanation | Session custom property was not loaded. |
Action | Ensure the session manager custom property value is correct and is not referencing an undefined variable. |
Explanation | You can use a persistent storage location when the user's session data must be maintained across a server restart, or when the user's session data is too valuable to lose through an unexpected server failure. When no persistent storage location is detected, HttpSession objects will strictly be stored in the local application server's memory. By default, no persistent storage location is available; it must be configured by the server administrator. |
Action | No action is required. If you intended to configure a persistent storage location, review the server logs and server configuration for errors. |
Explanation | You can use a persistent storage location when the user's session data must be maintained across a server restart, or when the user's session data is too valuable to lose through an unexpected server failure. When a persistent storage location is detected, HttpSession objects will be stored in the local application server's memory, and also persisted to the storage location. By default, no persistent storage location is available; it must be configured by the server administrator. |
Action | No action is required. If you did not intend to configure a persistent storage location, update your server configuration by removing all references to the storage location, and remove the feature required for the storage location from the Feature Manager. |
Explanation | The session data may be too large for the database column. |
Action | Reduce the size of this attribute before attempting to store it in the session or increase the value of the rowSizeLimit property. |
Explanation | The attribute name cannot be null. |
Action | Ensure that the attribute name is not null. |
Explanation | The attribute name contains at least one of the following separator characters, which cannot be used in the attribute name on the Cookie class: ( ) < > @ , ; : " / [ ] ? = { } |
Action | Ensure that the attribute name does not contain any separator characters and that the attribute name is valid. |