Explanation | The JMS Listener service has started successfully. |
Action | None |
Explanation | The JMS Listener service has stopped successfully. |
Action | None. |
Explanation | An exception occurred trying to initialize the JMS Listener. |
Action | Determine from the given exception the reason for the failure to initialize the JMS Listener. |
Explanation | An exception occurred trying to initialize the JMS Listener. |
Action | Determine from the given exception the reason for the failure to initialize the JMS Listener. |
Explanation | An exception occurred trying to create the MDBListener instance for the given JMS Listener. |
Action | Determine from the given exception the reason for the failure to create the MDBListener. Examine your JMS Listener config file to ensure the definition is correct, and ensure that all the necessary JMS resources are bound into the WebSphere JNDI name space. Also, ensure that the necessary JMS provider classes are in the Application Server classpath. |
Explanation | An exception occurred trying to create the MDBListener instance for the given JMS Listener. |
Action | Determine from the given exception the reason for the failure to create the MDBListener. Examine your JMS Listener config file to ensure the definition is correct, and ensure that all the necessary JMS resources are bound into the WebSphere JNDI name space. Also, ensure that the necessary JMS provider classes are in the Application Server classpath. |
Explanation | An exception occurred trying to start the JMS Listener. |
Action | Determine from the given exception the reason for the failure to start the JMS Listener. |
Explanation | An exception occurred trying to start the JMS Listener. |
Action | Determine from the given exception the reason for the failure to start the JMS Listener. |
Explanation | An exception occurred trying to terminate the JMS Listener. |
Action | If the exception indicates a serious failure, examine the reason for the error. |
Explanation | An exception occurred trying to parse the given JMS Listener config file. |
Action | Correct the problem in the JMS Listener config file and restart the EJB Server. |
Explanation | A warning was issued trying to parse the given JMS Listener config file. |
Action | Correct the problem in the JMS Listener config file and restart the EJB Server. |
Explanation | An error was issued trying to parse the given JMS Listener config file. |
Action | Correct the problem in the JMS Listener config file and restart the EJB Server. |
Explanation | An error was issued trying to parse the given JMS Listener config file. |
Action | Correct the problem in the JMS Listener config file and restart the EJB Server. |
Explanation | An exception occurred trying to parse the given JMS Listener config file. |
Action | Correct the problem in the JMS Listener config file and restart the EJB Server. |
Explanation | An exception occurred trying to parse the given JMS Listener config file. |
Action | Correct the problem in the JMS Listener config file and restart the EJB Server. |
Explanation | An exception occurred during postInvoke transaction completion processing after calling of the MDB.onMessage() method. |
Action | Examine the exception for reasons for the failure. |
Explanation | An exception occurred performing a JNDI lookup of a JMS resource. |
Action | Examine the exception for reasons for the failure. This might be due to the given JMS resource not being defined to the WebSphere JNDI namespace, or perhaps the necessary JMS provider classes are not in the Application Server classpath. |
Explanation | An exception has been reported by the JMS provider on a JMSConnection. |
Action | Examine the exception for reasons for the failure, then restart the MDB EJB jar module from the Administrative Console. |
Explanation | An exception has occurred during the start of the given MDB Listener. |
Action | Examine the exception for reasons for the failure, then restart the MDB EJB jar module from the Administrative Console. |
Explanation | An exception has occurred during the stop of the given MDB Listener. |
Action | Examine the exception for reasons for the failure, then try stopping the MDB EJB jar module again from the Administrative Console. |
Explanation | An exception has occurred during the creation of a MDB Listener. |
Action | Examine the exception for reasons for the failure, then restart the EJB Server to re-initialize the JMS Listener. |
Explanation | An attempt has been made to define a duplicate JMS Listener in the config file. |
Action | Correct the JMS Listener config file to remove the duplicate entry, then restart the EJB Server to re-initialize the JMS Listener. |
Explanation | During the stop of an MDB Listener, the closing of the listener caused the given exception. |
Action | If the exception indicates a serious failure, examine the reason for the error. |
Explanation | During the stop of an MDB Listener, the terminating of the listener caused the given exception. |
Action | If the exception indicates a serious failure, examine the reason for the error. |
Explanation | During the creation of an MDB Listener on a secure Application Server an exception occurred that indicated the given MessageDrivenBean did not have it's security permissions set. |
Action | Configure the MessageDrivenBean onMessage() method access permissions for access by anyone or the Server security ID. |
Explanation | During the invocation of the MessageDrivenBean.onMessage() method an unexpected exception occurred. |
Action | Examine the exception for reasons for the failure. After correction restart the MDB EJB jar module from the Administrative Console. |
Explanation | During the invocation of the MessageDrivenBean.onMessage() method an unexpected exception occurred. |
Action | Examine the exception for reasons for the failure. After correction restart the MDB EJB jar module from the Administrative Console. |
Explanation | During the creation of a JMS ServerSession for a new MDB Listener an unexpected exception occurred. |
Action | Examine the exception for reasons for the failure. After correction restart the MDB EJB jar module from the Administrative Console. |
Explanation | During the login processing on a secure Application Server an unexpected exception occurred. |
Action | Examine the exception for reasons for the security failure. After correction restart the MDB EJB jar module from the Administrative Console. |
Explanation | During the processing of a JMS message the JMS Listener was unable to being a transaction. |
Action | Examine the exception for reasons for the failure. After correction restart the MDB EJB jar module from the Administrative Console. |
Explanation | During the processing of a JMS message an unexpected exception occurred. |
Action | Examine the exception for reasons for the failure. After correction restart the MDB EJB jar module from the Administrative Console. |
Explanation | During the rollback of a JMS message an unexpected exception occurred. |
Action | Examine the exception for reasons for the failure and resolve the transaction using the Administrative Console. After correction restart the MDB EJB jar module from the Administrative Console. |
Explanation | During the committing of a JMS message an unexpected exception occurred. |
Action | Examine the exception for reasons for the failure. After correction restart the MDB EJB jar module from the Administrative Console. |
Explanation | During the rollback of a JMS message an unexpected exception occurred. |
Action | Examine the exception for reasons for the failure and resolve the transaction using the Administrative Console. After correction restart the MDB EJB jar module from the Administrative Console. |
Explanation | During the committing of a JMS message an unexpected exception occurred. |
Action | Examine the exception for reasons for the failure. After correction restart the MDB EJB jar module from the Administrative Console. |
Explanation | The given JMS Destination has reached its retry limit for the attempting to process a JMS message. |
Action | Examine the reason for the failure. After correction restart the MDB EJB jar module from the Administrative Console. |
Explanation | During the starting of a JMS ServerSession an unexpected exception occurred. |
Action | Examine the exception for reasons for the failure. After correction restart the MDB EJB jar module from the Administrative Console. |
Explanation | During the processing of a JMS message on a server thread an unexpected exception occurred. |
Action | Examine the exception for reasons for the failure. After correction restart the MDB EJB jar module from the Administrative Console. |
Explanation | During the processing of a JMS message on a server thread an unexpected exception occurred. |
Action | Examine the exception for reasons for the failure. After correction restart the MDB EJB jar module from the Administrative Console. |
Explanation | The JMS Listener service has started, however some warnings were issued during initialization. |
Action | Examine the warnings for any failures that might need correcting. |
Explanation | The JMS Listener service failed to start due to some initialization errors. |
Action | Examine the error logs for the reasons for the failures and then restart the server. |
Explanation | The given Message Bean Listener has started successfully. |
Action | None. |
Explanation | The given Message Bean Listener has stopped. |
Action | If the Listener has stopped unexpectedly, examine the application server logs for preceeding error messages. |
Explanation | The given Message Bean Listener has not being started because the Message Bean EJB with the given JNDI home name is not installed and started. |
Action | If the JMSListenerConfig.xml specifies an incorrect EJB JNDI home name then correct the entry and restart the server. |
Explanation | The initialization of the JMS Listener service failed due to some previous errors. |
Action | Examine the previous error messages to determine the reason for the failure and once corrected restart the server. |
Explanation | The binding of Message Driven Bean {0} to Listener Port {1} failed because the Listener Port could not be found. |
Action | Ensure the given Listener Port exists in the Message Listener Service for the given Application Server. |
Explanation | The given Message Driven Bean {0} does not have a MessageDrivenBeanBinding in its binding configuration. |
Action | Ensure the given MDB has being assembled and installed correctly, and then reinstall the MDB. |
Explanation | While activating a ListenerPort JMX MBean an exception occurred. |
Action | Examine the exception details to determine the reason for the failure, then restart the Application Server. |
Explanation | The start of the MDB listener failed, while being bound to the given Listener Port. |
Action | Examine the exception details to determine the reason for the failure, then restart the given listener port. |
Explanation | The message listener service checks that the current set of durable subscriptions are still valid and do not need unsubscribing. An exception occurred during this check. |
Action | Examine the exception details to determine the reason for the failure, then restart the server. |
Explanation | When an application is started that contains JMS durable subscriptions, the subscriptions are logged to ensure at a later stage they get cleaned up if the application is removed. An exception has occurred during this update. |
Action | Examine the exception details to determine the reason for the failure, then restart the server. |
Explanation | When attempting to unsubscribe a durable subscription an exception occurred. |
Action | Examine the exception details to determine the reason for the failure, then restart the server. |
Explanation | The durable subscription manager has determined the given subscription is now redundent, perhaps because the application has been removed, and the subscription has been unsubscribed. |
Action | None. |
Explanation | The late response message consumer was unable to write to the given log file, because of an exception. |
Action | Examine the exception details to determine why the log file could not be written to. |
Explanation | The late response message consumer was unable to read the given log file, because of an exception. |
Action | Examine the exception details to determine why the log file could not be read. |
Explanation | An MDB is being started against the given Listener Port which has a maximum sessions value larger than the JMS Connection Factory Session Pool size that it is configured to use. The MDB Listener will start using the Session Pool size. |
Action | Increase the JMS Connection Factory Session Pool size, or decrease the Listener Port maximum sessions. |
Explanation | An exception has been reported by the JMS provider on a JMSConnection. |
Action | Examine the exception for reasons for the failure, then restart the MDB EJB jar module from the Administrative Console. |
Explanation | The Listener Port has stopped due to error, but as the user has defined the max.recovery.retries and recovery.timeout.interval custom properties, the application server will attempt to restart it. |
Action | None. |
Explanation | The given Listener Port has reached its retry limit for starting |
Action | Examine the reason for the failure. After correction restart the Listener Port from the Administrative Console. |
Explanation | The activation config property is not a known property. This will be ignored and a warning message logged. |
Action | Ensure the property name is the correct and has not been spelt incorrectly. |
Explanation | This exception is unexpected. The cause is not immediately known. |
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 JNDI name for the destination in the listener port must match the destination JNDI name in the bindings. |
Action | Please ensure that the JNDI names for the destination match in both the listenerPort definition and the MDB's bindings. |
Explanation | An MDB is starting, which is bound to a listener port that specifies Java Naming Directory (JNDI) names for a default messaging JMS resource. Default messaging cannot be used by a listener port because it is a JMS resource adapter that supports activation specifications only. |
Action | Either redeploy the MDB against a default messaging JMS activation specification or redeploy the MDB against a different JMS resource that supports listener ports. |
Explanation | An MDB is starting, which is bound to a listener port that specifies Java Naming Directory (JNDI) names for a JMS resource adapter. JMS resource adapters cannot be used by a listener port because they support activation specifications only. |
Action | Either redeploy the MDB against a default messaging JMS activation specification or redeploy the MDB against a different JMS resource that supports listener ports. |
Explanation | The username and password were either unknown or did not have the required access priviliges |
Action | Check to ensure the username and password are correct |
Explanation | The priority specified was not in the range 0-9. |
Action | Ensure that the priority contains a valid value |
Explanation | The queue depth specified was not in the range 0-640000 |
Action | Ensure that the queue depth contains a valid value |
Explanation | The message length specified was not in the range |
Action | Ensure that the message length contains a valid value |
Explanation | The backout threshold specified was not in the range 0-999999999 |
Action | Ensure that the backout threshold contains a valid value |
Explanation | The Queue name specified was not valid |
Action | Ensure that the Queue name contains a valid value |
Explanation | The queue description specified was not valid |
Action | Ensure that the queue description contains a valid value |
Explanation | The Cluster name specified was not valid |
Action | Ensure that the cluster name contains a valid value |
Explanation | The cluster name list specified was not valid |
Action | Ensure that the cluster name list contains a valid value |
Explanation | The backout Queue name specified was not valid |
Action | Ensure that the backout Queue name contains a valid value |
Explanation | The remote Queue Manager name specified was not valid |
Action | Ensure that the remote Queue Manager name contains a valid value |
Explanation | The remote Queue name specified was not valid |
Action | Ensure that the remote Queue name contains a valid value |
Explanation | The transmission Queue name specified was not valid |
Action | Ensure that the queue name contains a valid value |
Explanation | The PCF response message is reporting that a parameter has caused an error, but the program does not know how to handle it. |
Action | Lookup the parameter in the MQSeries information centre and fix the problem. |
Explanation | The queue name specified was longer than 48 characters |
Action | Ensure that the queue name contains less than 48 characters. |
Explanation | The queue description specified was longer than 64 characters |
Action | Ensure that the queue description contains less than 64 characters. |
Explanation | The cluster name list specified was longer than 48 characters |
Action | Ensure that the cluster name list contains less than 48 characters. |
Explanation | The backout Queue name specified was longer than 48 characters |
Action | Ensure that the backout queue name contains less than 48 characters. |
Explanation | The Remote Queue Manager name specified was longer than 48 characters |
Action | Ensure that the Remote Queue Manager name contains less than 48 characters. |
Explanation | The cluster name specified was longer than 48 characters |
Action | Ensure that the cluster name contains less than 48 characters. |
Explanation | The transmission queue name specified was longer than 48 characters |
Action | Ensure that the transmission queue name contains less than 48 characters. |
Explanation | The PCF response message claims a parameter was too long, but the parameter was not expected |
Action | Check that the correct parameter is being used. Reference the MQSeries documentation if necessary. |
Explanation | An error has occurred that has not been recognised |
Action | Use the MQSeries Information Centre to discover what the error is. |
Explanation | The MB2MDB command has been invoked with an invalid -map option. |
Action | Correct the given -map option |
Explanation | The specified JMS Listener Config file contains no JMS listener definitions. |
Action | Specify a valid config file. |
Explanation | The specified EAR file is invalid as it does not contain the required file. |
Action | Specify a valid Enterprise Application ear file. |
Explanation | During the migration of the message bean application an exception occurred. |
Action | Examine the exception stack trace to determine the error and correct the problem. |
Explanation | The given EJB jar does not contain the required file. |
Action | Specify a valid EJB jar. |
Explanation | During the parsing of the given JMS Listener Config file an exception occurred. |
Action | Examine the exception stack trace to determine the error and correct the problem. |
Explanation | During the parsing of the given JMS Listener Config file warnings occurred. |
Action | Examine the warnings to determine the problem and correct it. |
Explanation | During the parsing of the given JMS Listener Config file errors occurred. |
Action | Examine the errors to determine the problem and correct it. |
Explanation | During the parsing of the given JMS Listener Config file errors occurred. |
Action | Examine the errors to determine the problem and correct it. |
Explanation | During the parsing of the given JMS Listener Config file an exception occurred. |
Action | Examine the exception stack trace to determine the error and correct the problem. |
Explanation | During the parsing of the given JMS Listener Config file an exception occurred. |
Action | Examine the exception stack trace to determine the error and correct the problem. |
Explanation | While trying to migrate the given message bean it was unable to create the given directory. |
Action | Examine the file system directory to determine why the directory could not be created. |
Explanation | While trying to migrate the given message bean it was unable to create the given file. |
Action | Examine the file system to determine why the file could not be created. |
Explanation | While compiling the generated MDB code an error occurred. |
Action | Examine the compiler errors messages to determine the problem. |
Explanation | While validating the input parameters the given input file was not found. |
Action | Correct the name of the given input file. |
Explanation | One of the settings had an invalid value. |
Action | Change the setting so it is valid. |
Explanation | The Queue is a transmission Queue and the user tried to make it a cluster Queue as well, this is not valid. |
Action | Remove the cluster name or cluster name list settings so it wont be a member of a cluster Queue. |
Explanation | The command failed, there are other error messages that will describe the cause of the problem. |
Action | Inspect the other error messages. |
Explanation | The Queue already existed. |
Action | The Queue was created elsewhere. Click OK again to modify the Queue. |
Explanation | The Queue name specified was not valid. |
Action | Change the Queue name so it is a valid name. |
Explanation | The Queue was open and the force option was not set. |
Action | Try again later when the Queue is not being used. |
Explanation | This exception is unexpected. The cause is not immediately known. |
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 | Unable to connect to the Queue manager. |
Action | Check that the Queue Manager and Command Server are running and that the settings you specified are correct. |
Explanation | The message was bigger than the maximum message length setting for the Queue. |
Action | Use MQSeries tooling to increase the maximum message length of the SYSTEM.ADMIN.COMMAND.QUEUE. |
Explanation | Either credentials were not specified or they were not valid. |
Action | Provide valid credentials to perform the action. |
Explanation | There were some messages on the Queue that could not be purged. |
Action | Try again later. |
Explanation | There was an error in a selector. |
Action | Try again later. |
Explanation | There was not enough main storage to perform the action. |
Action | Consult the MQSeries manuals to correct the problem. |
Explanation | An attempt to modify a Queue was made, but the Queue did not exist. |
Action | The Queue may have been deleted while you were editing its settings. Click OK to create the Queue. |
Explanation | While creating a Queue an error occurred that was not expected. |
Action | Refer to the MQSeries manuals to find a description of the error. |
Explanation | While sending a message an IO error occurred. |
Action | Try again later. |
Explanation | You tried to view a Queue that is not a local Queue. |
Action | Specify the name of a Queue that is a local Queue. |
Explanation | While unpacking the response from the Queue Manager an incorrect Queue setting was found. |
Action | Try again later. |
Explanation | While unpacking the response from the Queue Manager an incorrect type was found. |
Action | Try again later. |
Explanation | The Queue name specified is not valid. |
Action | Correct the name of the Queue. |
Explanation | An interanl error has occurred in the Queue Manager. |
Action | Try again later. |
Explanation | An internal error has occurred in the Queue Manager. |
Action | Try again later. |
Explanation | The Queue Manager name was either invalid or not known. |
Action | Check that the Queue Manager name is valid and that the Queue Manager exists. |
Explanation | The Queue Manager is not available. |
Action | Check that the Queue Manager is running and try again. |
Explanation | The Queue Manager is inactive. |
Action | Wait for the Queue Manager to be restarted and try again. |
Explanation | The Queue Manager is stopping. |
Action | Wait for the Queue Manager to be restarted and try again. |
Explanation | The Port number specifed was not a valid number. |
Action | Enter a valid number for the port and try again. |
Explanation | The Queue Depth specified was not a valid number. |
Action | Enter a valid number for the Queue Depth and try again. |
Explanation | The Maximum Message Length specified was not a valid number. |
Action | Enter a valid number for the Maximum Message Length and try again. |
Explanation | The Backout Threshold specified was not a valid number. |
Action | Enter a valid number for the Backout Threshold and try again. |
Explanation | The priority specified was not valid number. |
Action | Ensure that the priority contains a number. |
Explanation | The MQ Client was not installed and this is required to configure MQSeries. |
Action | Install the MQ Client. |
Explanation | The WMQQueueDefiner MBean was not supplied with a Queue Name |
Action | Specify the Name of the MQ Queue. |
Explanation | The WMQQueueDefiner MBean was not supplied with a Queue Manager Name. |
Action | Specify the Name of the MQ Queue Manager. |
Explanation | The WMQQueueDefiner MBean was not supplied with a Host Name. |
Action | Specify the Host Name the Queue Manager is running on. |
Explanation | The WMQQueueDefiner MBean was not supplied with a Host Name. |
Action | Contact your IBM Service Representative. |
Explanation | A null was specified for one of the Queue Data values. |
Action | Specify a value that is not null. |
Explanation | A String value was specified that was too short. |
Action | Specify a value that is long enough. |
Explanation | The Queue Name was set twice and this is not allowed. |
Action | Don't specify the Queue Name twice. |
Explanation | The value specified has a limited number of options, none of which were specified. |
Action | Specify a valid value. |
Explanation | A value was specified was outside the valid range. |
Action | Specify a number greater than or equal to zero. |
Explanation | The Cluster name specified was not valid. |
Action | Change the Cluster name so it is a valid name. |
Explanation | The Cluster Namelist specified was not valid. |
Action | Change the Cluster Namelist so it is a valid name. |
Explanation | The Backout Re-Queue Queue Name specified was not valid. |
Action | Change the Backout Re-Queue Queue Name so it is a valid name. |
Explanation | The Queue Description specified was not valid. |
Action | Change the Queue Description so it is a valid name. |
Explanation | One of the parameters contained an error, but it wasn't one of the expected ones. |
Action | Contact your IBM Service Representative. |
Explanation | A String value was specified that was too long. |
Action | Specify a value that is not too long. |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | None |
Action | None |
Explanation | The JMS resource binder for the given type of resource is disabled because the binder cannot resolve the necessary classes for this JMS resource type. |
Action | If this resource type is required to be supported, then check that the necessary JMS messaging components are installed and restart the application server. |
Explanation | The WebSphere MQ JMS client has not been installed. |
Action | Install the WebSphere MQ JMS client. |
Explanation | The WebSphere MQ JMS client has not been installed. |
Action | Install the WebSphere MQ JMS client and set the MQ_INSTALL_ROOT variable. |
Explanation | The name of the queue is too long. |
Action | Reduce the length of the queue name to the maximum number of characters allowed or less. |
Explanation | An error occurred while building a reference object for JNDI deployment. This error indicates an inconsistency in the resource definition. |
Action | Check the xml definition of the resource. |
Explanation | This exception is unexpected. The cause is not immediately known. |
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 | When attempting to define a JMS Destination to WebSphere Embedded Messaging the required classes could not be found on this node. |
Action | Install WebSphere Embedded Messaging or WebSphere MQ JMS on this node. |
Explanation | WebSphere MQ JMS Messaging will not be usable. |
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 | WebSphere MQ JMS has not been installed on this node so will not be available. |
Action | If WebSphere MQ JMS is to be used on this node it must be installed. |
Explanation | WebSphere MQ JMS Server has not been installed on this node so will not be available. |
Action | If a JMSServer is to be started on this node, WebSphere MQ JMS Server must be installed. |