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 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 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 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 | 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 | 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 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 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 | ID has not been provided for the messagingEngine tag. |
Action | No action is required. |
Explanation | ID is not specified for the destination, hence the destination will not be created. |
Action | Provide the ID for the destination. |
Explanation | fileStore tag has not been provided so default values will be taken while creating the filestore. |
Action | No action is required. |
Explanation | Messaging engine ID is unique to a messaging engine and cannot be changed while the server is active. |
Action | No action is required. |
Explanation | Messaging engine was not started during activate() call. Since the user has modified the server configuration file, an attempt will be made to start the messaging engine. |
Action | No action is required. |
Explanation | Initiating the JMS server start. |
Action | No action is required. |
Explanation | Startup of JMS server has completed successfully. |
Action | No action is required. |
Explanation | JMS server could not be started. |
Action | See the previous error messages during during an Messaging Engine start for further information. |
Explanation | No target destination provided for the alias destination. |
Action | Provide a valid target destination in the server configuration file. |
Explanation | Exception found during localization of destination. |
Action | See the previous messages and the state of messaging engine. |
Explanation | The specified destination could not be populated in cache. |
Action | See the previous messages for further information. |
Explanation | Configuration was not received from the server.xml file as its registration property (service.pid) which is used to identify the Managed Service or Managed Service Factory to the Configuration Admin service is null that means bundle cannot use declared service |
Action | See the accompanying error messages for further information on why messaging engine cannot be started. |
Explanation | This happens after ME is started but changes made won't be accepted as service.pid is null and therfore services are not invoked. |
Action | See the accompanying error messages related to Messaging Engine startup for further information. |
Explanation | Messaging engine configuration updation can lead to this type of error message if something goes wrong during this process. |
Action | See the accompanying error messages for further information. |
Explanation | The value specified for the defaultReliability parameter must be less than or equal to the value supplied for the maxReliability parameter. |
Action | Run the command again, specifying a defaultReliability value that is less than or equal to the maxReliability value. |
Explanation | The specified filestore path. |
Action | This message is for information purposes only. No action is needed. |
Explanation | A valid file path is required in server configuration file before the Messaging Engine can be started. |
Action | Correct the file path in server configuration file. |
Explanation | JMS server has stopped. |
Action | No action is required. |
Explanation | The messaging engine ID has been removed during modification of the server configuration file. The Messaging engine ID change will be ignored while the Messaging Engine is still active. |
Action | No action is required. |
Explanation | The same ID can not be used for multiple destinations, duplicate destinations will not be created. |
Action | Specify unique destination identifiers. |
Explanation | The log file size is greater than the permanent file store size. The file store size represents the combined size in megabytes for both permanent and temporary store. The file store size is equally divided between the permanent and temporary store, hence the log file size must be smaller than half of the size of the file store. |
Action | Increase the file store size or decrease the log file size. |
Explanation | The alias destination ID must be unique. |
Action | Ensure that you define a unique ID for the alias destination. |
Explanation | If the message does not give sufficient information, check previous messages for further help. |
Action | See the accompanying error messages for further information. |