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 | An instance of the channel framework service cannot be located. No network communication is possible. |
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 network connection was attempted, but failed because the Communications component cannot initialize correctly. |
Action | Examine the log files for your application server to determine why the Communications component did not correctly initialize. See any previous messages for further information. Correct the problem if possible. |
Explanation | The default outbound messaging channel chain is not defined to this application server. This application server may not be able to establish connections to remote gateway messaging engines. |
Action | Request that your administrator defines a default outbound messaging channel chain for this application server. |
Explanation | The default secure outbound messaging channel chain is not defined to this application server. This application server may not be able to establish connections to remote gateway messaging engines. |
Action | Request that your administrator defines a default secure outbound messaging channel chain for this application server. |
Explanation | The default tunneled outbound messaging channel chain is not defined to this application server. This application server may not be able to establish connections to remote gateway messaging engines. |
Action | Request that your administrator defines a default tunneled outbound messaging channel chain for this application server. |
Explanation | The default tunneled, secure outbound messaging channel chain is not defined to this application server. This application server may not be able to establish connections to remote gateway messaging engines. |
Action | Request that your administrator defines a default tunneled, secure outbound messaging channel chain for this application server. |
Explanation | The properties file containing information used when establishing secure client messaging connections cannot be located. A set of default values will be assumed. It may not be possible to establish secure client messaging connections. |
Action | Notify your administrator that they may need to supply a properties file for configuring client messaging transport level security. |
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 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 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 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 | No inbound messaging channel chains could be started, potentially because none have been defined to this application server. Messaging clients or other messaging engines 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 messaging. |
Explanation | An incorrect value for a channel configuration attribute has been specified. As a result the use of heartbeats for all communications over the associated channel chain has been disabled. |
Action | Notify your administrator that an incorrect heartbeat interval value has been specified. Request that they modify this value such that it is in the range of acceptable values. |
Explanation | An incorrect value for a channel configuration attribute has been specified. As a result the use of heartbeats for all communications over the associated channel chain has been disabled. |
Action | Notify your administrator that an incorrect heartbeat interval value has been specified. Request that they modify this value such that it is in the range of acceptable values. |
Explanation | An incorrect value for a channel configuration attribute has been specified. As a result the use of heartbeats for all communications over the associated channel chain has been disabled. |
Action | Notify your administrator that an incorrect heartbeat timeout value has been specified. Request that they modify this value such that it is in the range of acceptable values. |
Explanation | An incorrect value for a channel configuration attribute has been specified. As a result the use of heartbeats for all communications over the associated channel chain has been disabled. |
Action | Notify your administrator that an incorrect heartbeat timeout value has been specified. Request that they modify this value such that it is in the range of acceptable values. |
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 | A messaging engine has disconnected from this application server without following the expected disconnect protocols. |
Action | Notify your system administrator. |
Explanation | A client has disconnected from this application server without following the expected disconnect protocols. |
Action | Notify your system administrator. |
Explanation | A messaging engine connection from the specified host has been disconnected for transmitting invalid data. |
Action | Notify your system administrator. |
Explanation | A messaging engine connection from the specified host has been disconnected for transmitting invalid data. |
Action | Notify your system administrator. |
Explanation | A connection from the specified host has been disconnected for transmitting invalid data. |
Action | Notify your system administrator. |
Explanation | A connection from the specified host has been disconnected for transmitting invalid data. |
Action | Notify your system administrator. |
Explanation | A messaging engine connection from the specified host has been disconnected because it became unresponsive. |
Action | Notify your system administrator. |
Explanation | A connection from the specified host has been disconnected because it became unresponsive. |
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 detecting an error condition. |
Action | Examine the log files for your application server to determine why the connection was 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. |
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 | 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 detecting an error condition. |
Action | Examine the log files for your application server to determine why the connection was 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 | 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 | 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 | 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 network connection from host {0} on transport chain {1} terminated after incorrectly formatted information was received. |
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 | A new connection cannot be established due to a shortage of required resources. This problem is caused by a large number of active, established connections. |
Action | Attempt to reduce the resources used by applications by closing unneeded connections. |
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 | 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 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 | A network connection to the specified host name and port cannot be established. |
Action | Ask you administrator to determine if 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 | 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 information that is required to establish a Secure Sockets Layer (SSL)-based connection to a peer is not present in the current configuration. This information is normally obtained from a suitable transport chain definition. This chain definition has a name that matches a chain that is present on the remote peer. Such a transport chain cannot be found. It might not be possible to establish the connection. |
Action | Notify your system administrator that additional transport chains might need to be defined. |
Explanation | The information that is required to establish a Secure Sockets Layer (SSL)-based connection to a peer is not present in the current configuration. This information is normally obtained from a suitable transport chain definition. This chain definition has a name that matches a chain that is present on the remote peer. Such a transport chain cannot be found. It might not be possible to establish the connection. |
Action | Notify your system administrator that additional SSL transport channels to the specified transport chain might be required. |
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 | A messaging engine connection from the specified host has been disconnected because it became unresponsive. |
Action | Notify your system administrator. |
Explanation | A connection from the specified host has been disconnected because it became unresponsive. |
Action | Notify your system administrator. |
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 | Insufficient heap memory was available to store message data received from the specified remote process. The connection to the remote process was closed. |
Action | Investigate the message throughput, message size and load of your application server. Consider reducing message throughput, message size, application server load or increasing the amount of heap allocated by your server process. |
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 | If the message does not give sufficient information, check previous messages for further information. |
Action | If you are not able to resolve the problem ask your system administrator to help resolve the problem. |