Explanation | This exception is unexpected. The cause is not immediately known. |
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 exception is unexpected. The cause is not immediately known. |
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 messaging engine is capable of hosting managed persistent and managed non-persistent WS-ReliableMessaging. |
Action | No action is required. |
Explanation | This exception is unexpected. The cause is not immediately known. |
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 WS-ReliableMessaging JMX MBean service was unable to start on the messaging engine. Therefore the MBeans are not available. |
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 Web services application with the specified token has not responded within the specified period of time. The application resources on the messaging engine have therefore been unlocked and made available to other applications. |
Action | Investigate the application and ensure that it is still running. Check for any application-related errors. |
Explanation | A Web services application has been configured to use the specified messaging engine for storing reliable messaging state. The messaging engine has stopped so the request has been rejected. |
Action | Start the specified messaging engine. |
Explanation | A Web services application has been configured to use the specified messaging engine for storing reliable messaging state. When accessing the message store a resource error was encountered. This might include the message store being full. |
Action | Examine any related errors and correct if required. Restart the Web services application and reattempt the operation. |
Explanation | A Web services application has been configured to use the specified messaging engine for storing reliable messaging state. When accessing the message store a resource error was encountered. This might include the message store being full. |
Action | Examine any related errors and correct if required. Restart the Web services application and reattempt the operation. |
Explanation | A Web services application has been configured to use the specified messaging engine for storing reliable messaging state. When accessing the message store a resource error was encountered. This might include the message store being full. |
Action | Examine any related errors and correct if required. Restart the Web services application and reattempt the operation. |
Explanation | A Web services application has been configured to use the specified messaging engine for storing reliable messaging state. When accessing the message store a resource error was encountered. This might include the message store being full. |
Action | Examine any related errors and correct if required. Restart the Web services application and reattempt the operation. |
Explanation | A Web services application has been configured to use the specified messaging engine for storing reliable messaging state. When accessing the message store a resource error was encountered. This might include the message store being full. |
Action | Examine any related errors and correct if required. Restart the Web services application and reattempt the operation. |
Explanation | A Web services application has been configured to use the specified messaging engine for storing reliable messaging state. When accessing the message store a resource error was encountered. This might include the message store being full. |
Action | Examine any related errors and correct if required. Restart the Web services application and reattempt the operation. |
Explanation | A Web services application has been configured to use the specified messaging engine for storing reliable messaging state. When accessing the message store a resource error was encountered. This might include the message store being full. |
Action | Examine any related errors and correct if required. Restart the Web services application and reattempt the operation. |
Explanation | A Web services application is attempting to connect to the messaging engine to store reliable messaging state. The messaging engine cannot be contacted. The bus name or messaging engine name might have been specified incorrectly for the Web services application, or the messaging engine might not be running. |
Action | Check that the bus name and messaging engine name are specified correctly, and that the messaging engine is running. |
Explanation | A Web services application is attempting to connect to the messaging engine to store reliable messaging state. The messaging engine cannot be contacted. The bus name or messaging engine name might have been specified incorrectly for the Web services application, or the messaging engine might not be running. |
Action | Check that the bus name and messaging engine name are specified correctly, and that the messaging engine is running. |
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 closeSequence request is only supported in Version 1.1 of the reliable messaging specification. The application is using Version 1.0 of the specification so no action is undertaken in the reliable messaging runtime. |
Action | Either remove the call to closeSequence from the application, or update the policy set to use Version 1.1 of the reliable messaging specification. |
Explanation | If the message does not give sufficient information, check the accompanying messages. |
Action | See the accompanying error messages for further information. |