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 | Chains must contain transport channels to function. |
Action | Add some transport channels to {0}. |
Explanation | Channels can flow into (inbound) or out of (outbound) a server; all transport channels in a chain must flow in the same direction. |
Action | Ensure that all of the transport channels in chain {0} are either inbound or outbound channels; do not mix inbound and outbound in the same chain. |
Explanation | The first transport channel in an in inbound chain must be a connector channel. |
Action | Ensure that the first transport channel in the inbound chain is a connector channel. |
Explanation | The last transport channel in an inbound chain must be an acceptor channel. |
Action | Ensure that the last transport channel in the inbound chain is an acceptor channel. |
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 | Channels must provide a descriptor to map configuration types to runtime types; no matching descriptor could be found for configuration type {0}. |
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 | The Transport Channel Service has started the specified chain. |
Action | none |
Explanation | The Transport Channel Service has stopped the specified chain. |
Action | none |
Explanation | Inbound chains must be explicitly marked as enabled to be eligable for automatic startup. Disabled chains may still be started, but they must be explictly started by name. |
Action | none |
Explanation | The Transport Channel Service encountered an exception whilst attempting to discover and load its configuration; it will be started without configuration. |
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 Transport Channel Service could not locate its configuation. Default configuration for the Transport Channel Service should be added to server.xml. |
Action | Use the admin console or wsadmin to add default configuration for the Transport Channel Service. |
Explanation | The Transport Channel Service has been explicitly configured to be disabled and will not be started. |
Action | none |
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 | Channels must provide a descriptor to map configuration types to runtime types; no matching descriptor could be found for configuration type {0}. |
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 last transport channel in an outbound chain must be a connector channel. |
Action | Ensure that the last transport channel in the outbound chain is a connector channel. |
Explanation | An exception was caught in either the chain or underlying channels. |
Action | Ensure the right channels are being used in the chain. |
Explanation | An exception was caught in either the chain or underlying channels. |
Action | Ensure the right channels are being used in the chain. |
Explanation | An exception was caught in either the chain or underlying channels. |
Action | Ensure the right channels are being used in the chain. |
Explanation | An exception was caught in either the chain or underlying channels. |
Action | Ensure the right channels are being used in the chain. |
Explanation | The configured number of retries were not enough to cause the chain to start. |
Action | Ensure the port used by the chain is not already in use. Correctly set the custom properties for restarting chains. |
Explanation | The initial attempt to start a chain failed, but future attempts will be made to get it started. |
Action | Watch for an error or audit message indicating the result of the retry attempts. |
Explanation | The value of the property was out of the expected bounds. |
Action | Adjust the configuration to set the property to a valid value. |