Problem | 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/. |
Problem | One of the following could be the cause. The application containing the HandlerList has not been installed. The application containing the HandlerList has not been started. |
User response | If the application containing the HandlerList is not running then start it. Otherwise install the application containing the HandlerList or modify the mediation definition so it no longer references that handler list. |
Problem | 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/. |
Problem | The required environment for the mediation could not be created in order to invoke the mediation; the listed exception indicates the reason for this. |
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/. |
Problem | The required environment for the mediation could not be created in order to invoke the mediation for the message; the listed exception indicates the reason why the message could not be understood. |
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/. |
Problem | 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/. |
Problem | 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/. |
Problem | The required environment for the mediation could not be created in order to invoke the mediation for the message; the listed exception indicates the reason why the message could not be understood. |
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/. |
Problem | The required environment for the mediation could not be created in order to invoke the mediation for the message; the listed exception indicates the reason why the message could not be understood. |
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/. |
Problem | The mediation could not be applied to the message because the application that contains the mediation handlers did not start. |
User response | Start the application. |
Problem | The message to be mediated could not be retrieved in order to mediate it; the listed exception indicates the reason why the message could not be retrieved. |
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/. |
Problem | 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/. |
Problem | 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/. |
Problem | The required environment for the mediation could not be created in order to invoke the mediation for the message; the listed exception indicates the reason why the message could not be understood. |
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/. |
Problem | The required environment for the mediation could not be created in order to invoke the mediation for the message; the listed exception indicates the reason why the message could not be understood. |
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/. |
Problem | The required environment for the mediation could not be created in order to invoke the mediation for the message; the listed exception indicates the reason why the message could not be understood. |
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/. |
Problem | The bus has been configured with security enabled. In addition some mediations have been defined. When attempting to mediate a message the mediation framework discovered that the mediation authentication alias had not been defined. |
User response | Define an authentication alias and associate it with the bus's mediation authentication alias attribute. |
Problem | The bus has been configured with security enabled and the mediations authentication alias has been set. In addition some mediations have been defined. When attempting to mediate a message the authentication alias could not be resolved to a user ID and password. |
User response | Define the mediation authentication alias. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | After running the mediation, an attempt was made to commit the global transaction. However the transaction rolled back. |
User response | If the rollback was expected, this message is normal and can be ignored. If the rollback is unexpected, investigate the cause of the rollback. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | The application containing the handler is not be running. |
User response | Ensure that the application containing the handler is running. |
Problem | While executing the handler list a handler was encountered that did not implement the MediationHandler interface; the handler was not executed. |
User response | None. |
Problem | 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/. |
Problem | An attempt was made to mediate a message. As security has been enabled in order to do so the mediation authentication alias needs to be authenticated. |
User response | Ensure that the authentication alias represents a valid userid and password combination for your configured authentication registry. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | This message is output after a mediation handler list is not found and can be used to ensure that the correct handler list name is entered for the mediation definition. |
User response | Look through the list to see if the required handler list name is listed and if so update the mediation definition to reference that handler list. |
Problem | 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/. |
Problem | The mediation has completed successfully and returned with the value true to indicate that the message should continue in the bus. However when the system attempted to deliver the message to its next destination, it was unable to deliver the message as the next destination is unable to accept the message. |
User response | Investigate why the next destination is unable to accept the message. Once the problem with the next destination has been resolved, restart the mediation. |
Problem | The mediation has completed successfully and returned with the value true to indicate that the message should continue in the bus. However when the system attempted to make the message available to the consumers it was unable to do so. |
User response | Investigate why it is not possible to make the message available to the consumers. Once the problem with the next destination has been resolved, restart the mediation. |
Problem | The mediation has completed successfully and returned with the value true to indicate that the message should continue in the bus. However when the system attempted to send the message back to the messaging engine, the system reported that the connection was no longer unavailable. One cause of this condition is that the messaging engine is stopping. |
User response | If the messaging engine is stopping, no user response is required. Otherwise, investigate why the connection was lost. Once the problem with the connection has been resolved, restart the mediation. |
Problem | One of the following could be the cause. The application containing the HandlerList has not been installed. The application containing the HandlerList has not been started. |
User response | If the application containing the HandlerList is not running then start it. Otherwise install the application containing the HandlerList. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | 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/. |
Problem | The mediation handler required by the mediation handler list needs a class that cannot be located. The mediation will be stopped. |
User response | Investigate why the required class cannot be located. Once the problem has been resolved, restart the mediation. |
Problem | 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/. |
Problem | The required environment for the mediation could not be created in order to invoke the mediation. |
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/. |
Problem | The required environment for the mediation could not be created in order to invoke the mediation. |
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/. |
Problem | None |
User response | None |
Problem | None |
User response | None |
Problem | None |
User response | None |
Problem | None |
User response | None |
Problem | The message was given to a mediation, but the mediation threw the stated exception. As a result the mediation framework has rerouted the original version of the message to the exception destination. |
User response | None |
Problem | The message was given to a mediation, but the mediation changed the message so that the message either contains message properties that cannot be serialized, or its datagraph is no longer consistent with its format. As a result the mediation framework has rerouted the original version of the message to the exception destination. |
User response | None |
Problem | The message after mediating contained the empty forward routing path and a default forward routing path was specified for the destination being mediated; so the message was forwarded on the default forward routing path. |
User response | None |
Problem | The system attempted to trace details of a message being mediated, but the value of one of the user properties could not be displayed due to an exception. Mediation of the |
User response | If the exception is not expected, investigate the cause of the exception. |
Problem | The system attempted to trace the contents of a message being mediated, but was unable to do so. Mediation of the message will continue. |
User response | If the exception is not expected, investigate the cause of the exception. |
Problem | The message after mediating no longer contains a user property that was present before the message was given to the mediation. |
User response | None |
Problem | If the message does not give sufficient information, check previous messages for further help. |
User response | See previous messages for further information. |