WebSphere SOAP Channels messages |
WSSC1001I: The SOAP Monitor Channel has been configured.
Explanation:
The SOAP Monitor Channel has been successfully configured in the application server's channel framework environment.
User Response:
none
WSSC1002E: Could not find the Proxy Channel, aborting...
Explanation:
The SOAP Monitor Channel's configuration component could not locate the required Proxy Channel configuration, so it is unable to configure the SOAP Monitor Channel.
User Response:
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/.
WSSC1003E: Caught unexpected exception: {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WSSC1004E: Caught unexpected exception from asynchronous getRequestBodyBuffers(): {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WSSC1005E: Caught unexpected exception from synchronous getRequestBodyBuffers(): {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WSSC1006E: Caught unexpected exception from discriminate(): {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WSSC1007E: Caught unexpected exception during an asynchronous read operation: {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WSSC1008E: Caught unexpected exception while examining discrimination data: {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WSSC1009E: Caught unexpected exception while creating the SOAP monitor channel: {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WSSC1010E: Caught unexpected exception while instantiating class {0}, exception was: {1}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WSSC1011E: Class {0} does not implement interface {1}.
Explanation:
The SOAP monitor channel loaded the specified class because it was declared in the META-INF/soap-request-monitor file. The class is expected to implement the indicated interface, but it does not. Therefore, the class cannot be used by the SOAP monitor channel.
User Response:
Make sure that your META-INF/soap-request-monitor file declares the correct factory class name, and also make sure that your factory class name does not conflict with another class that is in the CLASSPATH.
WSSC1012E: Caught unexpected exception while obtaining SOAPRequestMonitorFactory instances: {0}
Explanation:
The SOAP monitor channel caught the specified exception while searching for searching for request monitor factory objects.
User Response:
Use the exception details to resolve the problem.
WSSC1013E: Caught unexpected exception while performing asynchronous operations: {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WSSC1014I: The SOAP acceptor channel buffer size is {0}.
Explanation:
This is simply an informational message.
User Response:
None.
WSSC1015E: Caught unexpected exception while creating the SOAP acceptor channel: {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WSSC1016E: Caught unexpected exception while attempting to delegate a SOAP request to the SOAP container: {0}
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WSSC1017E: The SOAP Container Service could not be found, therefore the SOAP acceptor channel cannot be configured.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WSSC1018E: The Web Container channel could not be found, therefore the SOAP acceptor channel cannot be configured.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WSSC1019I: The SOAP Acceptor Channel has been configured.
Explanation:
The SOAP Acceptor Channel has been successfully configured in the application server's channel framework environment.
User Response:
none
WSSC1020E: The SOAP Monitor Channel could not access the ChannelFramework Service.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.
WSSC1021E: The SOAP Acceptor Channel could not access the ChannelFramework Service.
Explanation:
This exception is unexpected. The cause is not immediately known.
User Response:
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/.