Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | This message indicates that previous problems prevent the initialization of the MQFAP channel, the exact problem preventing initialization of the channel may be indicated by previous error messages. |
Action | Ask your system administrator to examine the error and FFDC logs to help identify the reason for the problem. |
Explanation | No inbound MQ link channel chains could be started, potentially because none have been defined to this application server. MQ link clients or queue managers may not be able to successfully establish connections to this application server. |
Action | Notify your administrator that the application server may require additional inbound channel chains for the purposes of MQ interoperation. |
Explanation | The default MQ link outbound channel chain is not defined to this application server. This application server may not be able to establish connections to remote MQ queue managers. |
Action | Request that your administrator defines a default MQ link outbound channel chain for this application server. |
Explanation | The default secure MQ link outbound channel chain is not defined to this application server. This application server may not be able to establish connections to remote MQ queue managers. |
Action | Request that your administrator defines a default secure MQ link outbound channel chain for this application server. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A WebSphere MQ sender channel has disconnected from this application server without following the expected disconnect protocols. |
Action | Notify your system administrator. |
Explanation | A WebSphere MQ client application has disconnected from this application server without following the expected disconnect protocols. |
Action | Notify your system administrator. |
Explanation | Unexpected data has been received from a WebSphere MQ sender channel. A connection with the sender channel has been terminated. |
Action | Notify your system administrator. |
Explanation | Unexpected data has been received from a WebSphere MQ sender channel. A connection with the sender channel has been terminated. |
Action | Notify your system administrator. |
Explanation | A WebSphere MQ client application failed to send a heartbeat flow. It is possible that the client has terminated. The connection that was previously established with the client has been dropped. |
Action | If the WebSphere MQ client has not been intentionally terminated, notify your system administrator. |
Explanation | The specified sender channel for the specified MQLink could not establish a connection with the partner because a suitable listener is not available. |
Action | Notify your system administrator. |
Explanation | The specified sender channel for the specified MQLink could not establish a connection with the partner because the partner receiver channel is not available. It is possible that the receiver channel has not been defined or is in a STOPPED state. |
Action | Notify your system administrator. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/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 an error condition. |
Action | Examine the log files for your application server to determine why the connection closed. See any previous 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, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | A networking error occurred when attempting to establish a connection to the specified host. See the linked exception for further details. |
Action | Ask you administrator to verify that the specified host name is valid and that a process is listening for connections on the specified port. |
Explanation | This exception is unexpected. The cause is not immediately known. |
Action | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Explanation | The detection of an unexpected condition caused a network connection to close. |
Action | Examine any linked exceptions and the log files for your application server to determine why the network connection closed. See any previous messages for further information. Correct the problem if possible. |
Explanation | The detection of an unexpected condition caused a network connection to close. See any linked exception for further information. |
Action | Examine any linked exceptions and the log files for your application server to determine why the network connection closed. See any previous messages for further information. Correct the problem if possible. |
Explanation | If the message does not give sufficient information, check any previous messages for further information. |
Action | If you are not able to resolve the problem ask your systems administrator to help resolve the problem. |