Explanation | The specified messaging engine is commencing initialization. |
Action | No action is required. |
Explanation | An unexpected internal error occurred during system operation. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The SIB service has not been configured to start when the server process starts. |
Action | No action is required, unless you want to enable the SIB service. |
Explanation | The specified messaging engine has been disabled by administrative action and therefore will not be started. |
Action | Start the messaging engine if required. |
Explanation | The specified WCCM configuration document could not be loaded. This might cause other errors during runtime operation. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified destination could not be created. If JACL scripts or custom JMX programs were used to create the configuration, check these for errors. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The JMX MBean of the specified type and name could not be activated. Although this does not prevent the messaging server from starting, it does mean that any administrative functions that require the existence of this MBean might not work as expected. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified JMX MBean could not be deactivated. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified class could not be loaded. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The specified messaging engine has completed a stage of start or stop processing. |
Action | No action is required. |
Explanation | Bus configuration file changes are being processed. |
Action | No action is required. |
Explanation | All bus configuration file changes have been processed and all relevant destinations have been reloaded. |
Action | No action is required. |
Explanation | All messaging engine configuration documents are about to be checked for updates. |
Action | No action is required. |
Explanation | All messaging engine configuration documents have been read and updates have been processed. |
Action | No action is required. |
Explanation | Configuration document reloading has been enabled for the named bus. |
Action | No action is required. |
Explanation | The configuration of the property is not valid. |
Action | Run configuration validation. |
Explanation | The configuration of the property is not valid. |
Action | Run configuration validation. |
Explanation | The configuration of the property is not valid. |
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, undefine the HA_DISABLED environment variable then 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 then reissue 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 then reissue 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 then 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 then 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 then restart the server. |
Explanation | When reading the WCCM configuration document, an unexpected configuration was encountered. |
Action | The configuration might not be valid. 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 then restart the server. |
Explanation | An unexpected error occurred during engine initialization. The start phase is terminated and engine components that have already been started are stopped. |
Action | Check the logs to determine the error, correct the cause of the error then restart the server. |
Explanation | A messaging engine component could not be started. No other engine components will be started. |
Action | Check the logs to determine the error, correct the cause of the error then restart the server. |
Explanation | The specified messaging engine could not be stopped. |
Action | Check the logs to determine the error, correct the cause of the error then 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 then restart the server. |
Explanation | The messaging engine will not be able to run in this server. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The messaging engine did not activate, for the reason stated. |
Action | Refer to previous errors in the log. There are two common reasons for this problem. The first reason is that the messaging engine is unable to obtain a lock on its message store, due to it being locked by another active messaging engine. A message store can only be owned by one messaging engine. If this is the case, ensure that the messaging engine has sole access to the given message store. The second reason is that the database or filesystem share being used by the message store is unavailable. In this case, ensure that the database or filesystem share is active then re-enable the SIB service. |
Explanation | HAManager callback context was rejected, during the call to report completion of an asynchronous operation. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The messaging engine did not deactivate, for the reason stated. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The group name required by the messaging engine could not be created by HAManager. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | An Event Notification could not be sent from the 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, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The messaging engine is available for use. |
Action | No action is required. |
Explanation | The messaging engine is no longer available for use. |
Action | No action is required. |
Explanation | The messaging engine is reporting the error to HAManager, which will stop the server. With the Application Server Network Deployment, the server will be restarted if the nodeagent is monitoring it. With a network deployment 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 then correct it so that it does not recur. Either restart the server, or (if you are using network deployment) check that the automatic restart or failover has 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 the 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 | The messaging engine is being started. |
Action | No action is required. |
Explanation | The messaging engine is being stopped. |
Action | No action is required. |
Explanation | The messaging engine failed to start. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The messaging engine failed to stop. |
Action | If the problem persists, additional information might be available if you search for the message ID on the following Web sites: WebSphere Application Server Support page: http://www.ibm.com/software/webservers/appserv/was/support/ WebSphere Application Server for z/OS Support page: http://www.ibm.com/software/webservers/appserv/zos_os390/support/ . |
Explanation | The Messaging engine is in Joined state and available for failover. |
Action | No action is required. |
Explanation | The Messaging engine remains in disabled state as the ME re-enable count exceeded. |
Action | Refer WebSphere Application Sever documentation and manually enable the Messaging engine. |
Explanation | Before initiation the start of messaging engine the health of datastore is probed. |
Action | No action is required. |
Explanation | Probing connection to database resulted in success |
Action | No action is required. |
Explanation | Probing connection to database resulted in error |
Action | Check the connection to the database. |
Explanation | There was error getting datasource configid |
Action | No action is required. |
Explanation | Testing the connection to datasource |
Action | No action is required. |
Explanation | Testing the connection to datasource |
Action | No action is required. |
Explanation | Testing the connection to datasource |
Action | No action is required. |
Explanation | If its an authorization error then global error will be reported |
Action | No action is required. |
Explanation | If its not an authorization error then local error will be reported |
Action | No action is required. |
Explanation | HA Manager Service is unavailable, hence the messaging engine in the cluster will not have some HA features such as scalability and HA/Failover |
Action | Enable the HA Manager Service to resume the HA/Scalability features for the messaging engine |
Explanation | The messaging engine defined in the server is starting in synchronous mode. |
Action | No action is required. |
Explanation | The custom property sib.property.isMECritical of the messaging engine has the value true, so the messaging engine is defined as critical. |
Action | No action is required. |
Explanation | The custom property sib.property.isMECritical of the messaging engine does not have a boolean value, so the critical status cannot be evaluated. |
Action | Set the custom property sib.property.isMECritical of the messaging engine to a boolean value. |
Explanation | A messaging engine cannot start until the server has started. When the server has started, the messaging engine startup is completed. |
Action | No action required. |
Explanation | The messaging engine has finished the reconstitution and reconciliation of its destinations and links, and is waiting for the CRA start notification so that its startup can be completed. |
Action | No action is required. |
Explanation | The state check thread is started for messaging engine {0} started in synchronous start mode. |
Action | No action is required. |
Explanation | The critical messaging engine {0} has started in synchronous mode. |
Action | No action is required. |
Explanation | Returning the state check thread as no critical messaging engines are defined in server. |
Action | No action is required. |
Explanation | ME State Observer registered successfully for all messaging engines defined in the server. |
Action | No action is required. |
Explanation | ME State Observer notified successfully for all messaging engines defined in the server. |
Action | No action is required. |
Explanation | ME State Observer registered and notified successfully for all messaging engines defined in the server. |
Action | No action is required. |
Explanation | Messaging engine {0} notified all hagroup members to declare that it has started successfully |
Action | No action is required. |
Explanation | Passive Messaging engine {0} is notified by active instance as started since another instance in same HAGroup has already started. |
Action | No action is required. |
Explanation | If the message does not give sufficient information, check previous messages for further help. |
Action | See the accompanying error messages for further information. |