Explanation | The specified messaging engine is commencing initialization. |
Action | None. |
Explanation | An unexpected internal error occurred during system operation. |
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 SIB service has not been configured to start when the server process starts. |
Action | None, unless you want to enable the SIB service. |
Explanation | The specified messaging engine has been disabled by administrative action and will consequently not be started. |
Action | Start the messaging engine if required. |
Explanation | The specified WCCM configuration document could not be loaded. This may cause other errors during runtime operation. |
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 error occurred when attempting to create the specified destination. If JACL scripts or custom JMX programs were used to create the configuration, check these for errors. |
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 error occurred attempting to activate a JMX MBean with the specified type and name. Although this does not prevent the messaging server from starting, it does mean that any administrative functions which require the existence of this MBean, may not function as expected. |
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 error occurred attempting to deactivate a JMX MBean with the specified type and name. |
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 error occurred attempting to load the specified class. |
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 integrity error was detected when reading the WCCM configuration documents. If JACL scripts or custom JMX programs were used to create the configuration, check these for errors. |
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 specified messaging engine has completed a stage of start/stop processing. |
Action | None. |
Explanation | Bus configuration file changes are being processed. |
Action | None. |
Explanation | All bus configuration file changes have been processed and all relevant destinations have been reloaded. |
Action | None. |
Explanation | All messaging engine configuration documents are about to be checked for updates. |
Action | None. |
Explanation | All messaging engine configuration documents have been read and updates have been processed. |
Action | None. |
Explanation | The configuration document reloading has been enabled for the named bus. |
Action | None. |
Explanation | The configuration of the property is invalid. |
Action | Run configuration validation. |
Explanation | The configuration of the property is invalid. |
Action | Run configuration validation. |
Explanation | The configuration of the property is invalid. |
Action | Run configuration validation. |
Explanation | The SIB messaging components are not using HAManager GroupManager service because the HA_DISABLED environment variable is defined. |
Action | If HA operation is wanted, then undefine the HA_DISABLED environment variable and restart the server. |
Explanation | An attempt was made to start the specified messaging engine, but start is not a valid operation when the messaging engine is in the current state. This check prevents inadvertant manual start of a standby messaging engine in a cluster. |
Action | Check the state of the messaging engine and re-issue the operation when valid. |
Explanation | An attempt was made to start the specified messaging engine, but a serious error condition has previously been reported, so the messaging engine will not be restarted. |
Action | Restart the server or move the messaging engine to an alternate cluster server. |
Explanation | An attempt was made to stop the specified messaging engine, but stop is not a valid operation when the messaging engine is in the current state. |
Action | Check the state of the messaging engine and re-issue the operation when valid. |
Explanation | The messaging engine detected an error that is likely to recur on an alternate server, so failover will not be attempted. |
Action | Check the logs to determine the error, correct the cause of the error and restart the server. |
Explanation | The messaging engine detected a common mode error and is being automatically stopped. No failover will be attempted. |
Action | Check the logs to determine the error, correct the cause of the error and restart the server. |
Explanation | The messaging engine detected a common mode error and was automatically stopped. No failover will be attempted. |
Action | Check the logs to determine the error, correct the cause of the error and restart the server. |
Explanation | When reading the WCCM configuration document, an unexpected configuration was encountered. |
Action | The configuration is possibly invalid. Run WCCM validation to identify possible errors. |
Explanation | An unexpected error occurred during engine initialization. |
Action | Check the logs to determine the error, correct the cause of the error and restart the server. |
Explanation | An unexpected error occurred during engine initialization. The start phase is terminated and engine components that have already been started will be stopped. |
Action | Check the logs to determine the error, correct the cause of the error and restart the server. |
Explanation | An error occurred when starting an engine component. No other engine components will be started. |
Action | Check the logs to determine the error, correct the cause of the error and restart the server. |
Explanation | An error occurred when attempting to stop the messaging engine. |
Action | Check the logs to determine the error, correct the cause of the error and restart the server. |
Explanation | An error was detected by an engine component. |
Action | Check the logs to determine the error, correct the cause of the error and restart the server. |
Explanation | The messaging engine will not be able to run in this server. |
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 messaging engine did not activate, for the reason stated. |
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 | HAManager callback context was rejected, during the call to report completion of an asynchronous operation. |
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 messaging engine did not deactivate, for the reason stated. |
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 group name required by the messaging engine could not tbe created by HAManager. |
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 error occurred when attempting to send an Event Notification from a JMX MBean with the specified type and name. Although this does not prevent the continued operation of the messaging server, it does mean that this MBean cannot notify listeners of important messaging system events. |
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 Messaging Engine is available for use. |
Action | None. |
Explanation | The Messaging Engine is no longer available for use. |
Action | None. |
Explanation | The messaging engine is reporting the error to HAManager which will stop the server. With ND, the server will be restarted if the nodeagent is monitoring it. With an ND cluster, the messaging engine will failover to an alternate cluster server if the configured policy allows. |
Action | Check the logs to determine the cause of the error and correct it so that it does not recur. Either restart the server, or if using ND check that automatic restart/failover succeeded and the messaging engine is running. |
Explanation | The destination is set to maintain message ordering. Therefore concurrent mediations are not allowed and have been disabled. |
Action | If ordering is not required, unset the maintainMessageOrder attribute to disable concurrent mediation override. |
Explanation | The destination is set to maintain message ordering. Therefore the value for the receiveExclusive attribute has been overriden to become "true". |
Action | If ordering is not required, unset the maintainMessageOrder attribute to disable receiveExclusive override. |
Explanation | If the message does not give sufficient information, check previous messages for further help. |
Action | See previous messages for further information. |