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 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 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 | 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. |