Y SIbus mediation handlers messages |
CWSIY0001E: An internal error occurred. It is not possible to clone the message context: 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/.
CWSIY0002E: There is no environment entry defined with the name {0}.
Explanation:
The GenericEJBMediationHandler was unable to locate the mediation handler.
User Response:
Redeploy GenericEJBMediationHandler defining the missing environment entry.
CWSIY0003E: An internal error occurred. It is not possible to configure the mediation handler: 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/.
CWSIY0004E: The mediation handler class {0} cannot be loaded as specified by the {1} environment entry because the class {2} could not be located.
Explanation:
The GenericEJBMediationHandler was unable to load the class specified by the stated environment entry.
User Response:
Check the value of the environment entry. If is incorrect, redeploy GenericEJBMediationHandler. If the entry is correct, ensure that all of the classes required are available.
CWSIY0005E: The configured mediation handler {0} could not be constructed. Exception: {1}
Explanation:
The configured mediation handler cannot be constructed as it is either an interface, an abstract class, or does not have a constructor with no arguments.
User Response:
Ensure that the mediation handler is a non-abstract class with a constructor with no arguments.
CWSIY0006E: The configured mediation handler {0} or its constructor with no arguments is not visible. Exception: {1}
Explanation:
The configured mediation handler is either not public or it does not have a public constructor with no arguments.
User Response:
Ensure that the mediation handler is public and has a public constructor with no arguments.
CWSIY0007E: The configured mediation handler {0} threw an exception when setting the property {1} to value {2}. Exception: {3}.
Explanation:
When setting one of the mediation handler's properties an exception was caught.
User Response:
Ensure that the value is valid for the property being set.
CWSIY0008E: The mediation handler {0} has a property {1} defined in the deployment descriptor but the handler does not have a matching property.
Explanation:
A property was specified in the deployment descriptor but the handler does not have a matching property.
User Response:
Either remove the property from the deployment descriptor or add the property to the handler.
CWSIY0009E: The mediation handler {0}'s deployment descriptor has a property {1} defined as type {2} but the handler property is of type {3}.
Explanation:
A property specified in the deployment descriptor did not match the type defined for that property on the mediation handler.
User Response:
Either change the deployment descriptor so the types match, or change the property in the handler so they match.
CWSIY0010E: The mediation handler {0}'s deployment descriptor has a property {1} defined but the handler property is not settable.
Explanation:
A property was specified in the deployment descriptor but the mediation handler property of that name was not settable.
User Response:
Either remove the property from the deployment descriptor or add a set method for the property to the mediation handler.
CWSIY9999E: {0}
Explanation:
If the message does not give sufficient information, check previous messages for further help.
User Response:
See previous messages for further information.