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 | 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 | 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 | An operation was attempted on a connection resource that has previously been closed. This problem can result from an application programming error or because the system closed the connection resource in response to detecting an error condition. |
Action | Examine the log files for your application server to determine why the connection was closed. See the accompanying error messages for further information. Correct the problem if possible. |
Explanation | An operation was attempted on a connection resource that has previously been closed. This problem can result from an application programming error or because the system closed the connection resource in response to detecting an error condition. |
Action | Examine the log files for your application server to determine why the connection was closed. See the accompanying error messages for further information. Correct the problem if possible. |
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 connection to the remote messaging engine failed. This is possibly because the messaging engine is not started, or the port or host name specified was incorrect. |
Action | Ensure the messaging engine is running, the connection properties are correct and repeat the operation. |
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 | 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 | 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 | 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 | 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 | A method was invoked on a consumer, browser or producer session that had already been closed. |
Action | Ensure that the method call is performed before the session is closed. |
Explanation | A method was invoked on a connection object that had already been closed. |
Action | Ensure that the method call is performed before the connection is closed. |
Explanation | An attempt was made to register or unregister an asynchronous consumer callback for a consumer session that is started. |
Action | Ensure the consumer session is in a stopped state before attempting to register or unregister an asynchronous consumer callback. |
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 | An attempt was made to unlock an incorrect message in a locked message enumeration. |
Action | Before invoking the unlock method, make sure the locked message enumeration cursor is positioned on a message for which the unlock operation is valid. |
Explanation | An attempt was made to delete an incorrect message in a locked message enumeration. |
Action | Before invoking the delete method, make sure the locked message enumeration cursor is positioned on a message for which the delete operation is valid. |
Explanation | The maximum number of open sessions for a connection has been reached, and an attempt was made to open a further session. |
Action | Close any sessions that are not required and repeat the operation. |
Explanation | A synchronous consumer session method has been invoked while a asynchronous consumer callback is registered for the session. |
Action | Unregister the asynchronous consumer callback before invoking synchronous methods on a consumer session. |
Explanation | The invoked method is valid only on an in-process client and is not allowed to be called from a remote client. |
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 transaction becomes complete once commit or rollback has been called for the transaction. |
Action | Ensure commit or rollback are not called more than once on the same transaction object. |
Explanation | Connection to a remote messaging engine was successful, but the client and server cannot agree on appropriate connection values. |
Action | Ensure that the client is using valid connection values for the server you are connecting to and try again. |
Explanation | When attempting to log in, the server rejected the user information supplied. |
Action | Ensure the user information is correct and try again. |
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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | A method was invoked on a connection that has already been closed. |
Action | Ensure that the method call is performed before the connection is closed. |
Explanation | Only one receive() can be in progress at any one time per consumer session. |
Action | Ensure that only one receive method is called at a time on a consumer session. |
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 | 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 | A transaction becomes complete once commit or rollback has been called for the transaction. |
Action | Ensure commit or rollback are not called more than once on the same transaction object. |
Explanation | A transaction becomes complete once commit or rollback has been called for the transaction. |
Action | Ensure commit or rollback are not called more than once on the same transaction object. |
Explanation | This application server is now accepting messaging connection requests from clients and other messaging engines. |
Action | No action is required. |
Explanation | The server failed to run an unlockSet() command on behalf of the remote client. |
Action | Examine the error and FFDC logs to help determine the reason for the problem. |
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 server transport failed to initialize. The messaging engine may not be able to accept remote connections. |
Action | Examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to run an unlockSet() command on behalf of the remote client. |
Action | Examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | The server failed to run a deleteSet() or deleteAll() command on behalf of the remote client. |
Action | Examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | An operation performed within the transaction boundary failed. As such, this transaction has been rolled back to ensure integrity of data. The failure was logged in the system logs and a FFDC record was generated to help you diagnose the cause of the failure. |
Action | Examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | It was not possible to send a transacted or non-reliable message due to the stated exception. |
Action | Examine the error and FFDC logs to help determine the reason for the problem. |
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 server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to run a deleteSet() or deleteAll() command on behalf of the remote client. |
Action | Examine the error and FFDC logs to help determine the cause of the problem. |
Explanation | An operation performed within the transaction boundary failed. As such, this transaction has been rolled back to ensure integrity of data. The failure was logged in the system logs and a FFDC record was generated to help you diagnose the cause of the failure. |
Action | Examine the error and FFDC logs to help determine the cause of the problem. |
Explanation | The remote messaging engine has performed a controlled close of the connection. It may be shutting down, or there may be a problem with the network. |
Action | If the remote messaging engine was not shutting down verify the network is working correctly. Examine the error and FFDC logs to help determine the cause of the problem. |
Explanation | The server failed to run an unlockSet() command on behalf of the remote client. |
Action | Examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | The server failed to send data to or receive data from a remote client. The remote client may have been terminated or there may be a network problem. |
Action | If the client is still available and the network is working correctly, examine the error and FFDC logs to help determine the reason for this problem. |
Explanation | The server failed to run a deleteSet() or deleteAll() command on behalf of the remote client. |
Action | Examine the error and FFDC logs to help determine the reason for the problem. |
Explanation | The client connection described in the message has failed a security check. |
Action | Examine the error logs to determine why the specified client process cannot connect using the user identifier. |
Explanation | The connection described by the message failed because it referenced a messaging engine which was not available. |
Action | Examine the error logs to determine why the messaging engine was not available. |
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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | 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 | An operation was attempted on a connection resource that has previously been closed. This problem can result from an internal error or because the system closed the connection resource in response to detecting an error condition. |
Action | Examine the log files for your application server to determine why the connection was closed. See the accompanying error messages for further information and correct the problem if possible. |
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 is an information message. |
Action | No action is required. |
Explanation | This is an information message. |
Action | No action is required. |
Explanation | A channel exit running on the remote WebSphere MQ queue manager requested that channel be terminated. |
Action | Examine the error logs at the remote end of the link to determine why the remote exit ended the link. |
Explanation | The WebSphere MQ link may have been defined with an incorrect host name or port number or the channel definition is missing on the remote system. |
Action | Ensure the WebSphere MQ link has been configured to connect to the correct system and that a suitable channel definition with the correct name has been defined. |
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 remote queue manager is not currently running. |
Action | Either start the remote queue manager or retry the operation later. |
Explanation | The remote queue manager is ending and is therefore ending all of its connections. |
Action | No action is required. |
Explanation | The sequence wrap values at both ends of the link must be the same before the link can be started. |
Action | Change either end of the link to ensure the two sequence wrap values are the same and restart the link. |
Explanation | It could be that the synchronization information has become damaged or has been backed out to a previous version. If the situation cannot be resolved, the sequence number can be manually reset at the sending end of the link. |
Action | Determine whether either end of the link has been restored from a previous backup or deleted and redefined. If necessary issue a RESET command at the sending end to start the message sequence at a known point. |
Explanation | This is an information message. |
Action | No action is required. |
Explanation | This is an information message. |
Action | No action is required. |
Explanation | Channel connections must be defined in suitable pairs. For example, a sender should connect to a receiver or requester channel. |
Action | Check the WebSphere MQ link host name and port values to ensure that the link is configured to connect to the correct remote queue manager. Check that a suitable channel definition exists on the remote system. |
Explanation | It could be that the synchronization information has become damaged or has been backed out to a previous version. If the situation cannot be resolved, the sequence number can be manually reset at the sending end of the link. |
Action | Determine whether either end of the link has been restored from a previous backup or deleted and redefined. If necessary issue a RESET command to start the message sequence at a known point. |
Explanation | The specified MQ link sender channel failed to negotiate and establish a session with its partner WebSphere MQ receiver channel. The MQ link sender channel stops. |
Action | Examine the accompanying error messages to determine and resolve the cause of the failure. Alternatively, capture suitable diagnostic data and contact your local IBM Support Center. |
Explanation | A link or channel cannot connect and transfer messages to a remote system if it is currently indoubt with a different system. |
Action | Either restart the link to the original system or use the RESOLVE command to resolve the indoubt. |
Explanation | The remote system refused to accept one or more messages so the link has ended. |
Action | Examine the error files and logs of the remote system to determine why the message cannot be received, and then restart the link. |
Explanation | This is an informational message. |
Action | Check the message content of messages on the exception destination to determine why the messages were placed there. Use this information to resolve the problem. |
Explanation | This is an informational message. |
Action | Examine the logs for associated error messages that may provide details of the exception destination to which the undelivered messages were sent. Check the content of these messages to determine why they were placed there. Use this information to resolve the problem. |
Explanation | This is an informational message. |
Action | Check the message content of messages on the exception destination to determine why the messages were placed there. Use this information to resolve the problem. |
Explanation | This is an informational message. |
Action | Examine the logs for associated error messages that may provide details of the exception destination to which the undelivered messages were sent. Check the content of these messages to determine why they were placed there. Use this information to resolve the problem. |
Explanation | The channel might be stopped or the remote system does not have sufficient resources to run a further channel. |
Action | Check the remote system to ensure that the channel is available to run, and retry the operation. |
Explanation | The WebSphere MQ link sender channel named in the message has started. |
Action | No action is required. |
Explanation | The WebSphere MQ link sender channel named in the message has stopped. |
Action | No action is required. |
Explanation | The WebSphere MQ link receiver channel named in the message has started. |
Action | No action is required. |
Explanation | The WebSphere MQ link receiver channel named in the message has stopped. |
Action | No action is required. |
Explanation | A WebSphere MQ sender channel has connected to this application server from the specified host using the specified channel and transport chain. |
Action | No action is required. |
Explanation | A WebSphere MQ sender channel has disconnected from this application server. |
Action | No action is required. |
Explanation | The bus is configured to only allow connections through particular transport chains and this connection could not complete because the chain was not permitted. |
Action | Connect through a different transport chain, or configure the bus to allow connections through this chain. |
Explanation | The bus is configured to only allow connections through particular transport chains and this connection could not complete because the chain was not permitted. |
Action | Connect through a different transport chain, or configure the bus to allow connections through this chain. |
Explanation | The bus is configured to only allow connections through particular transport chains and this connection could not complete because the chain was not permitted. |
Action | Connect through a different transport chain, or configure the bus to allow connections through this chain. |
Explanation | The most likely cause of this error is if the target destination of the message exceeds the 48 character limit imposed by WebSphere MQ. |
Action | The message will have been placed on an exception destination. Check the message content to resolve the problem. |
Explanation | This is an informational message. |
Action | No action is required. |
Explanation | This is an informational message. |
Action | No action is required. |
Explanation | The WebSphere MQ link negotiates with the remote partner a maximum size for messages allowed down the link. If the size of a message exceeds this value, an attempt will be made to place the message on to the exception destination. |
Action | Check that the maximum message size values defined at either side of the link are sufficiently large for the configured applications. |
Explanation | The WebSphere MQ link negotiates with the remote partner a maximum size for messages allowed down the link. If the size of a message to be sent exceeds this maximum size, an attempt is made to send the message to an exception destination. |
Action | Examine the logs for associated error messages that may provide details of the exception destination to which the undelivered messages were sent. Examine the undelivered message if required, and ensure that the maximum message size values defined at either side of the link are sufficiently large for the configured applications. |
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 | 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 connection information in the connection name list is used to establish a connection with a WebSphere MQ queue manager. The connection name list provided is not valid. |
Action | Ensure a valid connection name list is given. Refer to the WebSphere Application Server Information Center for the valid syntax for a connection name list. |
Explanation | This is an informational message. |
Action | No action is required. |
Explanation | This is an informational message. |
Action | No action required. |
Explanation | This is an informational message. |
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 message was probably for a subscription request that has since terminated. Hence, the target destination is no longer available and the recoverable message cannot be delivered. |
Action | Refer to the WebSphere Application Server Information Center for details on how to clean up old subscriptions. |
Explanation | The message was probably for a subscription request that has since terminated. Hence, the target destination is no longer available. Non-recoverable messages cannot be delivered and have been discarded. |
Action | Refer to the WebSphere Application Server Information Center for details of how to clean up old subscriptions. |
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 | This is an informational message. |
Action | No action is required. |
Explanation | This is an informational message. |
Action | No action is required. |
Explanation | This is an informational message. |
Action | No action is required. |
Explanation | The inbound connection request identified a channel name which is not currently configured. |
Action | Ensure that the correct receiver channel names have been used in the WebSphere MQ link definitions and that the remote partner has been configured with the correct name in its channel definition. |
Explanation | This message either specifies the name of the failing MQ link sender channel, or explains the nature of a WebSphere MQ link failure. |
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 | This is an informational message. |
Action | No action is required. |
Explanation | During initialization of a WebSphere MQ link definition an unknown parameter was encountered. The unknown parameter will be ignored and initialization will continue. |
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 attempt was made to start a sender channel but the specified sender channel is already running on the specified MQ link. |
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 attempt to make use of a previously allocated connection to a messaging engine has failed because the connection has been dropped. It is possible that an MQ link or the messaging engine has been terminated. |
Action | Examine the error logs to determine why the connection could have been dropped. |
Explanation | An attempt to make use of a previously allocated connection to a messaging engine has failed because the connection has been lost. It is possible that an MQ link or the messaging engine has terminated. |
Action | Examine the error logs to determine why the connection could have been lost. |
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 | An MQ link sender channel has failed to encode a message destined for the specified queue and queue manager names so the message cannot be delivered to the target destination. The local and foreign bus names, as well as the associated exception, are also given. It is possible that some sort of internal error has occurred. Since the message cannot be formatted, it is possible that some names are not available. In which case, a value of '<unknown>' appears in the message text. |
Action | Examine any other messages that are issued in addition to this one to determine, and resolve, the cause of the failure. Alternatively, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The specified MQ link sender channel, defined in the specified MQ link, has received an error flow from the partner receiver channel. The MQ link sender may stop. |
Action | It is possible that the partner receiver channel has been stopped so this could be normal behaviour. Examine any other messages in the Application Server logs, or in the WebSphere MQ AMQERR* log files, to determine if there is a failure, and resolve the cause of the failure. Alternatively, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The specified MQ link sender channel, defined in the specified MQ link, has received an unexpected error from the partner receiver channel. The MQ link sender may stop. |
Action | For further information on resolving this error, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The specified MQ link sender channel, defined in the specified MQ link, is running with the specified CCSID and is not capable of converting to the partner's CCSID. The partner receiver channel is running with the specified CCSID and is not capable of converting to the MQ link sender's CCSID. |
Action | Ensure that the sender and receiver are running with supported CCSIDs. Alternatively, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The specified MQ link sender channel, defined in the specified MQ link, has received an error flow indicating that an authorization failure has occurred. |
Action | Ensure that the specified MQ link sender channel and its target WebSphere MQ receiver channel have matching security configuration parameters. Also examine the logs from either end of the channel in order to determine the cause of the failure. Alternatively, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The specified MQ link sender channel, defined in the specified MQ link, has received an error flow (indicating that a security error has occurred) because CipherSpec values specified at the two ends of the channel do not match, or because an incorrect CipherSpec value has been specified. |
Action | Ensure that the specified MQ link sender channel and its target WebSphere MQ receiver channel have matching security configuration parameters. Also examine the logs from either end of the channel in order to determine the cause of the failure. Alternatively, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The specified MQ link sender channel, defined in the specified MQ link, has received an error flow indicating that the peer name specified on the channel definition does not match the Distinguished Name in the certificate supplied, or is incorrect. |
Action | Ensure that the specified MQ link sender channel and its target WebSphere MQ receiver channel have matching security configuration parameters. Also examine the logs from either end of the channel in order to determine the cause of the failure. Alternatively, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The specified MQ link sender channel, defined in the specified MQ link, has received an error flow indicating no certificate was provided when one was expected due to SSL being enabled. |
Action | Ensure that the specified MQ link sender channel and its target WebSphere MQ receiver channel have matching security configuration parameters. Also examine the logs from either end of the channel in order to determine the cause of the failure. Alternatively, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The specified MQ link sender channel, defined in the specified MQ link, couldn't send a message to the default exception destination. |
Action | Check whether a default exception destination has been configured and if desired configure one. Alternatively, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The specified MQ link sender channel, defined in the specified MQ link, couldn't send a message to an exception destination. |
Action | Examine the logs for associated error messages that may provide details of the exception destination to which the undelivered message could not be sent. Ensure that a default, or link specific, exception destination is configured. If an exception destination is already configured, ensure that it is not full or disabled for sends. Alternatively, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The specified MQ link on the specified bus has started. |
Action | No action is required. |
Explanation | The specified MQ link on the specified bus has stopped. |
Action | No action is required. |
Explanation | The specified MQ link sender channel of the specified MQ link on the specified bus has started. |
Action | No action is required. |
Explanation | The specified MQ link sender channel of the specified MQ link on the specified bus has stopped. |
Action | No action is required. |
Explanation | The specified MQ link sender channel, of the specified MQ link on the specified bus, has started. A session has been established with a partner receiver channel on the specified remote queue manager. |
Action | No action is required. |
Explanation | The specified MQ link sender channel, of the specified MQ link on the specified bus, has stopped. The session with the partner receiver channel on the specified remote queue manager has ended. |
Action | No action is required. |
Explanation | The specified MQ link receiver channel, of the specified MQ link on the specified bus, has started. |
Action | No action is required. |
Explanation | The specified MQ link receiver channel, of the specified MQ link on the specified bus, has stopped. |
Action | No action is required. |
Explanation | The specified MQ link receiver channel, of the specified MQ link on the specified bus, has started. A session has been established with the partner sender channel on the specified remote queue manager. |
Action | No action is required. |
Explanation | The specified MQ link receiver channel, of the specified MQ link on the specified bus, has stopped. The session with the partner sender channel on the specified remote queue manager has ended. |
Action | No action is required. |
Explanation | A client connection with the specified user identifier was established from the specified network address. |
Action | No action is required. |
Explanation | A client connection with the specified user identifier has ended. |
Action | No action is required. |
Explanation | The specified MQ link receiver failed to send a message to the specified target queue. The target queue may be full, disabled for sends, undefined, or an attempt to create a producer session against it has failed for some reason. |
Action | Process messages on the queue if it is full. If the queue is not configured to allow messages to be sent to it, or if it is not defined, reconfigure it or define it, respectively. Alternatively,see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The specified MQ link sender was unable to start because the associated foreign bus could not be located. The MQ link will not be started. |
Action | Examine your MQ link sender configuration and ensure it is associated with a valid foreign bus. |
Explanation | The specified CCSID, supplied in an inbound connection request from a WebSphere MQ sender channel or a client, is unsupported. |
Action | Run with a supported CCSID. It is possible that the JVM that you are running with does not support the supplied CCSID. |
Explanation | This is an informational message. |
Action | No action required. |
Explanation | This is an informational message. |
Action | No action is required. |
Explanation | This is an informational message. |
Action | No action is required. |
Explanation | The system administrator has either changed the name of the WebSphere MQ link receiver channel, or has deleted the WebSphere MQ link receiver channel, hence the running instances of the WebSphere MQ link receiver channel have been stopped. |
Action | It is possible that no action is required. However, the associated partner WebSphere MQ sender channel(s) might have been left in an indoubt state, in which case resolve the indoubt channels appropriately. |
Explanation | The system administrator has either changed the name of the WebSphere MQ link receiver channel, or has deleted the WebSphere MQ link receiver channel, hence the running instances of the WebSphere MQ link receiver channel have been stopped. |
Action | It is possible that no action is required. However, the associated partner WebSphere MQ sender channel(s) might have been left in an indoubt state, in which case resolve the indoubt channels appropriately. |
Explanation | WebSphere MQ link receiver instances only pick up configuration settings when starting up. Thus any configuration changes made to a running WebSphere MQ link will not effect running WebSphere MQ link receiver instances. |
Action | If you wish the running WebSphere MQ link receiver instances to use the latest configuration changes then they either need to all be stopped before the changes are made, or they need to be stopped and restarted to pick up the changed configuration. |
Explanation | WebSphere MQ link senders pick up most configuration settings when going through the starting state. Thus, if a configuration change occurs, the changes are only picked up when the WebSphere MQ link sender next enters the starting state. This can be achieved by administratively stopping and starting the WebSphere MQ link sender, or changes will be picked up when the WebSphere MQ link sender next enters the starting state, perhaps due to retries occurring or the disconnect interval being reached. |
Action | If you want the WebSphere MQ link sender to use the latest configuration changes, either stop the MQ link sender before making the changes, or stop and restart the MQ link sender to pick up the new configuration. |
Explanation | The system administrator has either changed the name of the WebSphere MQ link sender, or has deleted the WebSphere MQ link sender. Hence the running WebSphere MQ link sender has been stopped. |
Action | It is possible that no action is required. However, the deleted WebSphere MQ link sender may now be in an indoubt state and so may need to be resolved. |
Explanation | The configuration for the named WebSphere MQ link has been deleted, but the named WebSphere MQ link sender is still in an indoubt state. The deletion cannot fully complete until the indoubt state is resolved. |
Action | Use the administrative tooling to resolve the indoubt state which will allow the deletion of the named WebSphere MQ link to complete. |
Explanation | An attempt was made to create an Object Store with a negative initial size. |
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 attempt was made to create an Object Store with a negative maximum size. |
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 attempt was made to create an Object Store with an initial size that was less than the origin of the Object Store. |
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 attempt was made to create an Object Store with an initial size that was greater than the maximum size. |
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 attempt was made to retrieve an object from the Object Store, but an object version mismatch was encountered. |
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 attempt was made to remove an object from the Object Store, but an object version mismatch was encountered. |
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 attempt was made to locate an object in the Object Store, but the supplied object index was found to be less than the origin of the Object Store. |
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 attempt was made to locate an object in the Object Store, but no suitable object was found for the supplied object index. |
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 attempt was made to remove an object from the Object Store, but the supplied object index was found to be less than the origin of the Object Store. |
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 attempt was made to remove an object from the Object Store, but no suitable object was found for the supplied object index. |
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 attempt was made dump entries in the Object Store, but the supplied number of entries to be dumped was found to be negative. |
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 attempt was made to rollback an indoubt batch of messages while the stated WebSphere MQ link sender was still running. |
Action | Stop the stated WebSphere MQ link sender and repeat the action. |
Explanation | An attempt was made to commit an indoubt batch of messages when the stated WebSphere MQ link sender was still running. |
Action | Stop the stated WebSphere MQ link sender and repeat the action. |
Explanation | An attempt was made to commit an indoubt batch of messages when there was no indoubt batch of messages. |
Action | No action is required. |
Explanation | An attempt was made to rollback an indoubt batch of messages when there was no indoubt batch of messages. |
Action | No action is required. |
Explanation | An attempt was made to move or delete a message with the stated id but it could not be completed as it was part of an indoubt batch. |
Action | Consider rolling the batch back if the message needs to be moved or deleted. Otherwise no action is necessary unless the batch remains in the indoubt state for an extended period of time. |
Explanation | An attempt was made to move or delete a message with the stated id but it could not be completed as the stated WebSphere MQ link sender is not in the stopped state. |
Action | Consider stopping the stated WebSphere MQ link sender if the message needs to be moved or deleted. Otherwise no action is necessary. |
Explanation | An attempt was made to move or delete messages but the stated messages could not be moved or deleted as they were part of an indoubt batch. |
Action | Consider rolling the batch back if the messages need to be moved or deleted. Otherwise no action is necessary unless the batch remains in the indoubt state for an extended period of time. |
Explanation | An attempt was made to move or delete messages but it couldn't be completed as the stated WebSphere MQ link sender is not in the stopped state. |
Action | Consider stopping the stated WebSphere MQ link sender if the messages need to be moved or deleted. Otherwise no action is necessary. |
Explanation | An attempt was made to test a foreign bus connection when the stated WebSphere MQ link sender channel was running. |
Action | Stop the stated WebSphere MQ link sender channel in state STOPPED, then repeat the test connection request. |
Explanation | An attempt was made to test a foreign bus connection but a WebSphere MQ link sender channel has not been configured for the stated WebSphere MQ link. |
Action | Configure a WebSphere MQ link sender channel on the stated MQ link, then repeat the test connection request. |
Explanation | An attempt was made to test a foreign bus connection but the stated WebSphere MQ link sender channel was unable to create a data flow for subsequent transfer to the partner receiver channel on the stated remote host. |
Action | An internal error has occurred. For further information on resolving this error, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | An attempt was made to test a foreign bus connection but a connection could currently not be established to the stated remote host on the stated port. It is possible that there is some sort of transitory resource constraint. |
Action | Repeat the action at a later point in time. For further information on resolving this error, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The ping channel function is used when testing a foreign bus connection. This function involves sending data to the partner receiver channel. The partner receiver channel is expected to return the data that it receives but it has not done so. |
Action | Try repeating the test connection request. For further information on resolving this error, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | An attempt was made to test a foreign bus connection but the partner receiver channel did not respond within the inbuilt timeout period. It is possible that the remote host is unavailable, or cannot be reached due to network delays. |
Action | Determine why the remote host is unavailable. Repeat the action when the remote host is available and listening on the stated port. |
Explanation | An attempt was made to test a foreign bus connection but the partner receiver channel has requested closure of the channel. |
Action | Determine why the partner receiver channel has requested closure, resolve the issue then repeat the test connection request. |
Explanation | An attempt was made to test a foreign bus connection but the WebSphere MQ link sender channel encountered an unrecoverable communications error. |
Action | It is possible that this is a transient error. Try repeating the test connection request. For further information on resolving this error, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The ping channel function is used when testing a foreign bus connection. This function involves sending data to the partner. The partner is expected to return the data that it receives but it has not returned any data. |
Action | Try repeating the test connection request. For further information on resolving this error, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | The ping channel function is used when testing a foreign bus connection. This function involves sending ping channel data to the partner which, in turn, returns the data. A problem has been encountered while converting the ping channel data into the stated encoding. |
Action | Ensure that the Java Virtual Machine (JVM) you are running with supports the specified encoding. For further information on resolving this error, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |
Explanation | All WebSphere MQ functionality has been disabled on this server as a result of the 'disable WebSphere MQ functionality' check box being selected on a WebSphere MQ messaging provider panel at an appropriate scope. Alternatively the manageWMQ administrative command may have been used to disable WebSphere MQ functionality. As a result of this all WebSphere MQ link functionality has been disabled. |
Action | None unless WebSphere MQ link functionality is required, in which case clear the 'disable WebSphere MQ functionality' check box on the relevant WebSphere MQ messaging provider panel or make use of the manageWMQ administrative command. |
Explanation | All WebSphere MQ functionality has been disabled on the server running the named WebSphere MQ link as a result of the 'disable WebSphere MQ functionality' check box being selected on a WebSphere MQ messaging provider panel at an appropriate scope. Alternatively the manageWMQ administrative command may have been used to disable WebSphere MQ functionality. As a result of this all WebSphere MQ link functionality has been disabled. |
Action | None unless WebSphere MQ link functionality is required, in which case clear the 'disable WebSphere MQ functionality' check box on the relevant WebSphere MQ messaging provider panel or make use of the manageWMQ administrative command. |
Explanation | During initialization of an MQClientLink object, an unknown parameter was encountered. The unknown parameter will be ignored and initialization will continue. |
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 WebSphere MQ connection described in the message has failed a security check. |
Action | Examine the error logs to determine why the specified WebSphere MQ process cannot connect using the user identifier. |
Explanation | The WebSphere MQ connection described by the message failed because it referenced a queue manager name which did not correspond to an active MQClientLink. |
Action | Examine the error logs to determine why the MQClientLink is not available. |
Explanation | The WebSphere MQ connection described by the message failed because it referenced a channel name which did not correspond to the channel parameter in the named MQClientLink. |
Action | Examine the error logs to determine what the correct channel name should be. |
Explanation | A WebSphere MQ client application has connected to this application server from the specified host using the specified transport chain. |
Action | No action is required. |
Explanation | A WebSphere MQ client has disconnected from this application server. |
Action | No action is required. |
Explanation | While processing a request for connection from a client, the Messaging Engine associated with an SICoreConnection object could not be found. It is possible that the Messaging Engine has terminated, or is no longer a member of the bus, and hence the connection has been lost. |
Action | Examine the error logs to determine why the Messaging engine is no longer available. |
Explanation | An attempt to make use of a previously allocated connection to a Messaging Engine has failed because the connection has been dropped. It is possible that client or Messaging Engine has terminated. |
Action | Restart the client or Messaging Engine if required, alternatively, examine the error logs to determine why the connection could have been dropped. |
Explanation | An attempt to make use of a previously allocated connection to a Messaging Engine has failed because the connection has been lost. It is possible that client or Messaging Engine has terminated. |
Action | Restart the client or Messaging Engine if required, alternatively, examine the error logs to determine why the connection could have been lost. |
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 WebSphere MQ connection described by the message failed because it referenced a queue manager name which did not correspond to an active MQClientLink. |
Action | Determine why an MQClientLink object does not exist for the specified queue manager. Define one if required. |
Explanation | The WebSphere MQ connection described by the message failed because it referenced a channel name which did not correspond to an active MQClientLink. |
Action | Determine why an MQClientLink object does not exist for the specified channel. Define one if required. |
Explanation | A connection from a WebSphere MQ client has been lost. This may be due to a communications failure. It is possible that the WebSphere MQ client application has terminated. |
Action | Restart the WebSphere MQ client if required, otherwise ask your system administrator to determine why the connection could have been dropped. |
Explanation | All WebSphere MQ functionality has been disabled on this server as a result of the 'disable WebSphere MQ functionality' check box being selected on a WebSphere MQ messaging provider panel at an appropriate scope. Alternatively the manageWMQ administrative command may have been used to disable WebSphere MQ functionality. As a result of this all WebSphere MQ client link functionality has been disabled. |
Action | None unless WebSphere MQ client link functionality is required, in which case clear the 'disable WebSphere MQ functionality' check box on the relevant WebSphere MQ messaging provider panel or make use of the manageWMQ administrative command. |
Explanation | A remote call was made to the core API that generated an exception. However, the exception was not recognized or expected at this time. |
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 method call was made on the client that should only be called on the server. |
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 attempt was made to set a property but the value supplied was incorrect for the property. |
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 attempt was made to encode a string using a specified encoding, but this failed because the encoding was unsupported. |
Action | Correct the encoding value and repeat the operation. |
Explanation | The string cannot be sent across the network as it exceeds the length of strings which may be sent using the messaging protocols. |
Action | Correct the string to reduce its length and repeat the operation. |
Explanation | The remote server generated an exception that caused a FFDC. |
Action | Examine the exception and the corresponding FFDC file on the server to determine the problem and retry your operation. |
Explanation | An attempt was made to set a property but the value supplied was incorrect for the property. |
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 | Handshaking information was received that was not understood. |
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 messaging engine handshake has failed due to an incorrect property. |
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 attempt was made to set a property but the value supplied was incorrect for the property. |
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 client handshake has failed due to an incorrect property. |
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 attempt was made to set a property but the value supplied was incorrect for the property. |
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 attempt was made to set a property but the value supplied was incorrect for the property. |
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 client connection with the specified user identifier was established from the specified network address. |
Action | No action is required. |
Explanation | A client connection with the specified user identifier has ended. |
Action | No action is required. |
Explanation | An attempt was made to set a property but the value supplied was incorrect for the property. |
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 attempt was made to set a property but the value supplied was incorrect for the property. |
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 | 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 | 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 | An attempt was made to encode a string using a specified encoding, but this failed because the encoding was unsupported. |
Action | Correct the encoding value and repeat the operation. |
Explanation | If the message does not give sufficient information, check previous messages for further help. |
Action | For further information on resolving this error, see the problem determination information on the Application Server Support Web page: http://www.ibm.com/software/webservers/appserv/was/support. |