WebSphere JMS ServerMSGS0001E: Starting the JMS Server failed with exception: {0}
Explanation
A problem occurred while starting the JMS Server. Previous messages will contain information about the problem.
User Response:
See previous messages for more information about the problem.
MSGS0011W: No JMSSERVER_QUEUED_ADDRESS EndPoint port specified - the default value will be used
Explanation
There was no port property specified for the JMSSERVER_QUEUED_ADDRESS Endpoint for the JMS Server configuration. The default value will be used.
User Response:
Correct the configuration of the JMS Server.
MSGS0012W: No JMSSERVER_DIRECT_ADDRESS EndPoint port specified - the default value will be used
Explanation
There was no port property specified for the JMSSERVER_DIRECT_ADDRESS Endpoint for the JMS Server configuration. The default value will be used.
User Response:
Correct the configuration of the JMS Server.
MSGS0013W: No numThreads value specified - the default value will be used
Explanation
There was no numThreads value specified in the JMS Server configuration. The default value will be used.
User Response:
Correct the configuration of the JMS Server.
MSGS0014E: Two or more of the JMS Server port values are the same so the JMS Server can not be started
Explanation
The port properties specified for the JMSSERVER_QUEUED_ADDRESS and JMSSERVER_DIRECT_ADDRESS EndPoints and the securityPort for the JMS Server configuration must be unique but two or more were found to be the same.
User Response:
Correct the configuration of the JMS Server.
MSGS0015W: No securityPort specified - the default value will be used
Explanation
There was no port property specified for the securityPort in the JMS Server configuration. The default value will be used.
User Response:
Correct the configuration of the JMS Server.
MSGS0016W: JMS Server MBean registration failed with exception: {0}
Explanation
The JMS Server was unable to register its MBean, you may experience problems administering the JMS Server.
User Response:
Investigate the reason why the MBean could not be registered.
MSGS0017E: The JMS Server is performing a recovery termination due to a JMS Provider problem
Explanation
The JMS Server is terminating because a part of the JMS Provider was not functioning correctly. This situation may result from a previous abnormal termination of the JMS Server. The recovery termination will clean up the JMS Provider.
User Response:
The JMS Server will be restarted by the NodeAgent. Check the log for previous error messages indicating the cause of the failure.
MSGS0018E: The JMS Server failed to obtain access to its EndPoints because of exception: {0}
Explanation
The JMS Server was unable to access its configuration information and will terminate.
User Response:
Correct the configuration of the JMS Server.
MSGS0050I: Starting the Queue Manager
Explanation
This is an informational message.
User Response:
No action required.
MSGS0051I: Queue Manager open for business
Explanation
This is an informational message.
User Response:
No action required.
MSGS0052I: Starting the Broker
Explanation
This is an informational message.
User Response:
No action required.
MSGS0053I: Broker open for business
Explanation
This is an informational message.
User Response:
No action required.
MSGS0054I: Stopping the Broker
Explanation
This is an informational message.
User Response:
No action required.
Explanation
This is an informational message.
User Response:
No action required.
MSGS0056I: Stopping the Queue Manager
Explanation
This is an informational message.
User Response:
No action required.
MSGS0057I: Queue Manager is stopped
Explanation
This is an informational message.
User Response:
No action required.
MSGS0058E: Unable to start the JMS Server as WebSphere Embedded Messaging has not been installed
Explanation
The current Execution State for the JMS Server is START however WebSphere Embedded Messaging has not been installed on this node so the JMS Server could not be started.
User Response:
Change the Execution State of the WebSphere JMS Server to STOP or install WebSphere Embedded Messaging on this node.
MSGS0059E: Unable to bind to port {0} - a JMS Server using the port may already be running on this node
Explanation
The JMS Server was unable to bind to the specified TCP/IP port number during initialization. This may be because another JMS Server has already bound to the same port or some other application may be using this port.
User Response:
Check your system to determine if another JMS Server is already running and using this port. Ensure that no other applications on your system are using this port. You may also change the JMS Server configuration and have the JMS Server use a different port.
MSGS0100E: Start Queue Manager failed with exception: {0}
Explanation
The JMS Server was unable to create a new system process for the internal WebSphere MQ Queue Manager, the internal WebSphere Queue Manager was not started.
User Response:
Investigate the reason why a system process could not be created. The problem may be caused by insufficient system resources.
MSGS0101E: Start Queue Manager command failed with exit code: {0}
Explanation
The JMS Server received a non-zero exit code from the internal WebSphere MQ Queue Manager process, the internal WebSphere Queue Manager was not started. Exit code 16 or 72 indicates a configuration problem. Exit code 39 indicates a down-level version of MQSeries was found. Exit code 69 indicates insufficient memory. Exit code 101 indicates insufficient disk space. Exit code 71 indicates an internal error.
User Response:
Investigate the reason why the internal WebSphere MQ Queue Manager process failed. For exit codes 16 and 72 check the createmq.log file in the logs directory. For exit code 39 check the mq_install.log. For exit codes 69 and 101 check and increase the system resources. For exit code 71 check the WebSphere MQ Queue Manager error logs and if the problem persists contact IBM.
MSGS0102E: Start Queue Manager Command Server failed with exception: {0}
Explanation
The JMS Server was unable to create a new system process for the internal WebSphere MQ Queue Manager Command Server. The internal WebSphere Queue Manager will not be usable.
User Response:
Investigate the reason why a system process could not be created. The problem may be caused by insufficient system resources.
MSGS0103E: Start Command Server command failed with exit code: {0}
Explanation
The JMS Server received a non-zero exit code from the internal WebSphere MQ Queue Manager Command Server process. The internal WebSphere Queue Manager will not be usable. An exit code 101 means that there was insufficient disk space available.
User Response:
Investigate the reason why the internal WebSphere MQ Queue Manager Command Server process failed. Check the WebSphere MQ Queue Manager error logs. The problem may be caused by insufficient system resources.
MSGS0104E: Queue Manager Listener failed with exit code: {0}
Explanation
The JMS Server received a non-zero exit code from the internal WebSphere MQ Queue Manager Listener process. The internal WebSphere Queue Manager will not be usable. An exit code 101 means that there was insufficient disk space available.
User Response:
Investigate the reason why the internal WebSphere MQ Queue Manager Listener process failed. Check the WebSphere MQ Queue Manager error logs. The problem may be caused by insufficient system resources.
MSGS0105E: Queue Manager Listener failed rc: {0}
Explanation
The JMS Server received a non-zero exit code from the internal WebSphere MQ Queue Manager Listener process. The internal WebSphere Queue Manager will not be usable. An exit code 101 means that there was insufficient disk space available. Another possible cause is that the JMS Server QueuedPort is already in use.
User Response:
Investigate the reason why the internal WebSphere MQ Queue Manager Listener process failed. Check the WebSphere MQ Queue Manager error logs. The problem may be caused by insufficient system resources. If the JMS Server QueuedPort is already in use, change it to use a different value.
MSGS0106E: Start Queue Manager Listener failed with exception: {0}
Explanation
The JMS Server was unable to create a new system process for the internal WebSphere MQ Queue Manager Listener. The internal WebSphere Queue Manager will not be usable.
User Response:
Investigate the reason why a system process could not be created. The problem may be caused by insufficient system resources.
MSGS0107E: End Command Server command failed with exit code: {0}
Explanation
The JMS Server received a non-zero exit code from the internal WebSphere MQ Queue Manager Command Server process when attempting to end the Command Server. The JMS Server will still end.
User Response:
Restart the JMS Server and shut it down again. If this is not successful, the internal WebSphere MQ Queue Manager Command Server process may require manual termination.
MSGS0108E: End Queue Manager Command Server failed with exception: {0}
Explanation
The JMS Server was unable to end the internal WebSphere MQ Queue Manager Command Server process. The JMS Server will still end.
User Response:
Restart the JMS Server and shut it down again. If this is not successful, the internal WebSphere MQ Queue Manager Command Server process may require manual termination.
MSGS0109E: End Queue Manager command failed with exit code: {0}
Explanation
The JMS Server received a non-zero exit code from the internal WebSphere MQ Queue Manager when attempting to end the Queue Manager. The JMS Server will still end.
User Response:
Restart the JMS Server and shut it down again. If this is not successful, the internal WebSphere MQ Queue Manager processes may require manual termination.
MSGS0110E: End Queue Manager failed with exception: {0}
Explanation
The JMS Server was unable to end the internal WebSphere MQ Queue Manager. The JMS Server will still end.
User Response:
Restart the JMS Server and shut it down again. If this is not successful, the internal WebSphere MQ Queue Manager processes may require manual termination.
MSGS0111E: End Queue Manager Listener command failed with exit code: {0}
Explanation
The JMS Server received a non-zero exit code from the internal WebSphere MQ Queue Manager Listener process when attempting to end the Listener. The JMS Server will still end.
User Response:
Restart the JMS Server and shut it down again. If this is not successful, the internal WebSphere MQ Queue Manager Listener process may require manual termination.
MSGS0112E: End Queue Manager Listener failed with exception: {0}
Explanation
The JMS Server was unable to end the internal WebSphere MQ Queue Manager Listener process. The JMS Server will still end.
User Response:
Restart the JMS Server and shut it down again. If this is not successful, the internal WebSphere MQ Queue Manager Listener process may require manual termination.
MSGS0113E: The Queue Manager is no longer available - MQException: {0}
Explanation
The JMS Server was unable to connect to the internal WebSphere MQ Queue Manager because the Queue Manager is no longer available. The JMS Server will not be usable.
User Response:
Investigate the reason why the internal WebSphere MQ Queue Manager failed. Check the WebSphere MQ Queue Manager error logs. The problem may be caused by insufficient system resources.
MSGS0114E: Queue Manager Listener failed rc: {0}
Explanation
The JMS Server was unable to connect to the internal WebSphere MQ Queue Manager Listener process because the Listener is no longer available. The internal WebSphere Queue Manager will not be usable.
User Response:
Investigate the reason why the internal WebSphere MQ Queue Manager Listener failed. Check the WebSphere MQ Queue Manager error logs. The problem may be caused by insufficient system resources.
MSGS0115E: Queue Manager Listener failed rc: {0}
Explanation
The JMS Server was unable to connect to the internal WebSphere MQ Queue Manager Listener process because the Listener is no longer available. The internal WebSphere Queue Manager will not be usable.
User Response:
Investigate the reason why the internal WebSphere MQ Queue Manager Listener failed. Check the WebSphere MQ Queue Manager error logs. The problem may be caused by insufficient system resources.
MSGS0116W: End Queue Manager trace failed with exit code: {0}
Explanation
The JMS Server was unable to end the tracing of the internal WebSphere MQ Queue Manager.
User Response:
Check the WebSphere MQ Queue Manager error logs. The problem may be caused by insufficient system resources.
MSGS0117W: End Queue Manager trace failed with exception: {0}
Explanation
The JMS Server was unable to end the tracing of the internal WebSphere MQ Queue Manager.
User Response:
Check the WebSphere MQ Queue Manager error logs. The problem may be caused by insufficient system resources.
MSGS0118W: Set Queue Manager trace failed with exit code: {0}
Explanation
The JMS Server was unable to start the tracing of the internal WebSphere MQ Queue Manager.
User Response:
Check the WebSphere MQ Queue Manager error logs. The problem may be caused by insufficient system resources.
MSGS0119W: Set Queue Manager trace failed with exception: {0}
Explanation
The JMS Server was unable to start the tracing of the internal WebSphere MQ Queue Manager.
User Response:
Check the WebSphere MQ Queue Manager error logs. The problem may be caused by insufficient system resources.
MSGS0120W: Set Queue Manager trace to all failed with exit code: {0}
Explanation
The JMS Server was unable to start full tracing of the internal WebSphere MQ Queue Manager.
User Response:
Check the WebSphere MQ Queue Manager error logs. The problem may be caused by insufficient system resources.
MSGS0121W: Set Queue Manager trace to all failed with exception: {0}
Explanation
The JMS Server was unable to start full tracing of the internal WebSphere MQ Queue Manager.
User Response:
Check the WebSphere MQ Queue Manager error logs. The problem may be caused by insufficient system resources.
MSGS0122W: Queue Manager Command Server did not end
Explanation
The internal WebSphere MQ Queue Manager Command Server process did not end normally. The JMS Server will still end.
User Response:
Restart the JMS Server and shut it down again. If this is not successful, the internal WebSphere MQ Queue Manager Command Server process may require manual termination.
MSGS0123W: Queue Manager did not end so force stopped
Explanation
The internal WebSphere MQ Queue Manager did not end normally so was force stopped by the JMS Server. The JMS Server will still end.
User Response:
Restart the JMS Server and shut it down again. If this is not successful, the internal WebSphere MQ Queue Manager may require manual termination.
MSGS0124E: Force stop Queue Manager failed with exception: {0}
Explanation
The internal WebSphere MQ Queue Manager did not end when force stopped by the JMS Server. The JMS Server will end.
User Response:
Restart the JMS Server and shut it down again. If this is not successful, the internal WebSphere MQ Queue Manager may require manual termination.
MSGS0125W: Queue Manager Listener did not end
Explanation
The internal WebSphere MQ Queue Manager Listener process did not end normally. The JMS Server will still end.
User Response:
Restart the JMS Server and shut it down again. If this is not successful, the internal WebSphere MQ Queue Manager Listener process may require manual termination.
MSGS0126E: Start QMQM subsystem failed with exception: {0}
Explanation
The JMS Server was unable to create a new system process for starting the internal WebSphere MQ Queue Manager subsystem. The internal WebSphere Queue Manager will not be usable.
User Response:
Investigate the reason why a system process could not be created. The problem may be caused by insufficient system resources.
MSGS0127E: Check object failed with exception: {0}
Explanation
The JMS Server was unable to create a new system process for checking the internal WebSphere MQ Queue Manager subsystem description. The internal WebSphere Queue Manager will not be usable.
User Response:
Investigate the reason why a system process could not be created. The problem may be caused by insufficient system resources.
MSGS0128E: Start QMQM subsystem command failed
Explanation
The QMQM subsystem cannot be started because it does not exist. The Integral JMS Provider is not installed. The internal WebSphere Queue Manager will not be usable.
User Response:
Install the Integral JMS Provider.
MSGS0129E: User not authorized to start Queue Manager (command failed with exit code: {0})
Explanation
The JMS Server received a non-zero exit code from the internal WebSphere MQ Queue Manager process, indicating an authorization problem while starting the process. The internal WebSphere Queue Manager was not started.
User Response:
Investigate the authorization error. In particular, check membership of the mqm and mqbrkrs groups.
MSGS0152E: Unable to define JMS Destination {0} as the Queue name is too long - maximum length is {1} characters
Explanation
The name of the queue is too long.
User Response:
Reduce the length of the queue name to the maximum number of characters allowed or less.
MSGS0153E: The Queue Manager process {0} could not be started - error: {1}
Explanation
The JMS Server was unable to start the internal WebSphere MQ Queue Manager.
User Response:
On Windows platforms, if the error was that a file or directory could not be found, ensure the file exists and is in the path.
MSGS0200E: The Broker DataFlowEngine return code was: {0}
Explanation
The JMS Server received a non-zero return code from the internal WebSphere MQ Broker. The internal WebSphere MQ Broker was not started. The JMS Server will not be usable for publish/subscribe.
User Response:
Investigate the reason why the internal WebSphere MQ Broker failed. Check the WebSphere MQ Broker error logs. The problem may be caused by insufficient system resources.
MSGS0201E: Unable to start the Broker because WebSphere Embedded Messaging Server support not been installed
Explanation
The current Execution State for the JMS Server is START however WebSphere Embedded Messaging has not been installed on this node so the JMS Server will not be usable for publish/subscribe.
User Response:
Change the Execution State of the WebSphere JMS Server to STOP or install WebSphere Embedded Messaging on this node.
MSGS0202E: The correct Broker level has not been installed
Explanation
The current Execution State for the JMS Server is START however the level of the WebSphere Embedded Messaging Broker installed on this node is not correct. The internal WebSphere MQ Broker was not started. The JMS Server will not be usable for publish/subscribe.
User Response:
Change the Execution State of the WebSphere JMS Server to STOP or install the correct level of the WebSphere Embedded Messaging Broker on this node.
MSGS0203E: Illegal Access exception occurred while calling Broker start
Explanation
The JMS Server was unable to start the internal WebSphere MQ Broker because an Illegal Access Exception occurred. The internal WebSphere MQ Broker was not started. The JMS Server will not be usable for publish/subscribe.
User Response:
Check the WebSphere MQ Broker error logs. If the problem persists report the problem to IBM.
MSGS0204E: Invocation Target exception occurred while calling Broker start
Explanation
The JMS Server was unable to start the internal WebSphere MQ Broker because an Invocation Target Exception occurred. The internal WebSphere MQ Broker was not started. The JMS Server will not be usable for publish/subscribe.
User Response:
Check the WebSphere MQ Broker error logs. If the problem persists report the problem to IBM.
MSGS0250I: Broker had not been started
Explanation
This is an informational message.
User Response:
No action required.
MSGS0251W: Broker Manager unable to disconnect from Queue Manager - MQException: {0}
Explanation
An exception occurred when the JMS Server attempted to disconnect from the internal WebSphere MQ Queue Manager. This problem may occur if the Queue Manager is prematurely terminated.
User Response:
Check the WebSphere MQ Queue Manager error log.
MSGS0252E: The Broker has terminated unexpectedly
Explanation
During a routine check the JMS Server detected that the internal Publish/Subscribe Broker has terminated. The JMS Server will no longer be usable for publish/subscribe.
User Response:
Check the WebSphere Embedded Messaging Publish Subscribe Broker error logs.
MSGS0253E: Broker Manager unable to attach to Queue Manager - Queue Manager does not exist
Explanation
The JMS Server could not connect to the internal WebSphere MQ Queue Manager because the required Queue Manager does not exist. The JMS Server will not be usable.
User Response:
Check the createmq.log file in the logs directory. Check the WebSphere MQ Queue Manager error logs.
MSGS0254E: Broker Manager unable to attach to Queue Manager - Queue Manager is not running
Explanation
The JMS Server could not connect to the internal WebSphere MQ Queue Manager because the required Queue Manager is not running. The JMS Server will not be usable.
User Response:
Check the WebSphere MQ Queue Manager error logs.
MSGS0255E: Broker Manager unable to attach to Queue Manager - unknown Queue
Explanation
The JMS Server could not connect to the internal WebSphere MQ Queue Manager because a required queue does not exist. The JMS Server will not be usable for publish/subscribe.
User Response:
Check the createmq.log file in the logs directory. Check the WebSphere MQ Queue Manager error logs.
MSGS0256E: Broker Manager unable to attach to Queue Manager - MQException on connect: {0}
Explanation
An exception occurred when the JMS Server attempted to connect to the internal WebSphere MQ Queue Manager. The JMS Server will not be usable for publish/subscribe.
User Response:
Check the WebSphere MQ Queue Manager error logs.
MSGS0257E: Broker Manager unable to attach to Queue Manager - MQException opening queue: {0}
Explanation
An exception occurred when the JMS Server attempted to open a queue on the internal WebSphere MQ Queue Manager. The JMS Server will not be usable for publish/subscribe.
User Response:
Check the WebSphere MQ Queue Manager error logs.
MSGS0258E: Broker Manager unable to send startup message to Broker - MQException: {0}
Explanation
An exception occurred when the JMS Server attempted to send a startup configuration message to the internal Publish/Subscribe Broker. The JMS Server will not be usable for publish/subscribe.
User Response:
Check the WebSphere MQ Queue Manager error logs.
MSGS0259W: Broker Manager unable to send message to Broker - MQException: {0}
Explanation
An exception occurred when the JMS Server attempted to send a startup configuration message to the internal Publish/Subscribe Broker. The JMS Server will not be usable for publish/subscribe.
User Response:
Check the WebSphere MQ Queue Manager error logs.
MSGS0260E: Broker Manager unable to create startup message for Broker: {0}
Explanation
An exception occurred when the JMS Server attempted to create a startup configuration message for the internal Publish/Subscribe Broker. The JMS Server will not be usable for publish/subscribe.
User Response:
Check the WebSphere MQ Queue Manager error logs.
MSGS0261W: Broker Manager unable to create message for Broker: {0}
Explanation
An exception occurred when the JMS Server attempted to create a startup configuration message for the internal Publish/Subscribe Broker. The JMS Server will not be usable for publish/subscribe.
User Response:
Check the WebSphere MQ Queue Manager error logs.
MSGS0262W: Broker Manager unable to send shutdown message to Broker - MQException: {0}
Explanation
An exception occurred when the JMS Server attempted to send a shutdown message to the internal Publish/Subscribe Broker. The JMS Server will still end.
User Response:
Check the WebSphere MQ Queue Manager error logs.
MSGS0263W: Broker Manager unable to send message to Broker - MQException: {0}
Explanation
An exception occurred when the JMS Server attempted to send a shutdown message to the internal Publish/Subscribe Broker. The JMS Server will still end.
User Response:
Check the WebSphere MQ Queue Manager error logs.
MSGS0264W: Broker Manager unable to create shutdown message for Broker: {0}
Explanation
An exception occurred when the JMS Server attempted to send a shutdown message to the internal Publish/Subscribe Broker. The JMS Server will still end.
User Response:
Check the WebSphere MQ Queue Manager error logs.
MSGS0265W: Broker Manager unable to create message for Broker: {0}
Explanation
An exception occurred when the JMS Server attempted to send a shutdown message to the internal Publish/Subscribe Broker. The JMS Server will still end.
User Response:
Check the WebSphere MQ Queue Manager error logs.
MSGS0266W: Request to Broker failed - see service log for reply text
Explanation
A request sent to the internal Publish/Subscribe Broker failed. The JMS Server may not be usable for publish/subscribe.
User Response:
Check the WebSphere Embedded Messaging Publish Subscribe Broker error logs.
MSGS0267W: Unexpected exception in getReply - MQException: {0}
Explanation
An exception occurred when the JMS Server attempted to read a reply message from the internal Publish/Subscribe Broker. The JMS Server may not be usable for publish/subscribe.
User Response:
Check the WebSphere MQ Queue Manager and WebSphere Embedded Messaging Publish Subscribe Broker error logs.
MSGS0268W: Unable to read reply message from Broker: {0}
Explanation
An exception occurred when the JMS Server attempted to read a reply message from the internal Publish/Subscribe Broker. The JMS Server may not be usable for publish/subscribe.
User Response:
Check the WebSphere MQ Queue Manager and WebSphere Embedded Messaging Publish Subscribe Broker error logs.
MSGS0269E: Error starting DataFlowEngine - Exception: {0}
Explanation
An exception occurred when the JMS Server attempted to start the internal Publish/Subscribe Broker. The JMS Server will not be usable for publish/subscribe.
User Response:
Check the WebSphere Embedded Messaging Publish Subscribe Broker error logs.
MSGS0270E: Error reading reply from Broker - see previous messages and exceptions
Explanation
An exception occurred when the JMS Server attempted to read a reply from the internal Publish/Subscribe Broker. The JMS Server may not be usable for publish/subscribe.
User Response:
Check the WebSphere Embedded Messaging Publish Subscribe Broker error logs.
MSGS0271E: Broker Manager unable to check request queue - MQException: {0}
Explanation
An exception occurred when the JMS Server attempted to check on the progress of the internal Publish/Subscribe Broker. The JMS Server may not be usable for publish/subscribe.
User Response:
Check the WebSphere MQ Queue Manager error logs.
MSGS0272E: The Broker is not processing request messages
Explanation
The internal Publish/Subscribe Broker is not processing requests from the JMS Server. The JMS Server may not be usable for publish/subscribe.
User Response:
Check the WebSphere Embedded Messaging Publish Subscribe Broker error logs.
MSGS0300E: An error occurred building the reference for JNDI deployment of {0}
Explanation
An error occurred while building a reference object for JNDI deployment. This error indicates an inconsistency in the resource definition.
User Response:
Check the xml definition of the resource.
MSGS0301E: An exception occurred building the reference for JNDI deployment of {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MSGS0302E: Unable to define Queue {0} as WebSphere Embedded Messaging has not been installed
Explanation
When attempting to define a queue to WebSphere Embedded Messaging the required classes to connect to WebSphere Embedded Messaging could not be found on this node.
User Response:
Install WebSphere Embedded Messaging on this node.
MSGS0303E: Unable to define JMS Destination {0} as neither WebSphere Embedded Messaging nor MQSeries JMS is available
Explanation
When attempting to define a JMS Destination to WebSphere Embedded Messaging the required classes could not be found on this node.
User Response:
Install WebSphere Embedded Messaging or WebSphere MQ JMS on this node.
MSGS0305W: Unable to define JMS Destination {0} - see error log or debug trace for details
Explanation
The Queue could not be defined on the given JMS Server.
User Response:
See previous message for details.
MSGS0350E: There is no JMS Server on node {0}, server {1}
Explanation
WebSphere JMS Provider Queues can not be defined on a node and server where there is no JMS Server defined.
User Response:
Ensure the JMS Server has been properly defined on the given node and server. Check the appropriate createmq log.
MSGS0351W: The JMS Server on node {0}, server {1} is not running
Explanation
The JMS Server on the given node and server is not running.
User Response:
Start the JMS Server on the given node and server.
MSGS0352W: Unable to list the Queues for the JMS Server on this node
Explanation
It was not possible to list the Queues defined.
User Response:
See previous messages for further information.
MSGS0353E: Queue name {0} contains invalid characters so the Queue could not be defined
Explanation
Valid characters for a Queue name are: A-Z a-z 0-9 . / _ %.
User Response:
Change the name field of the Queue definition to a valid name.
MSGS0354E: Unable to define or delete Queue {0} for PCF reason {1}
Explanation
It was not possible to delete or define the Queue.
User Response:
See previous messages for further information. If the error persists report the problem to IBM.
MSGS0355W: The deletion or creation of Queue {0} may not have completed
Explanation
No response was received from the request to delete or define the queue. The queue may not have been deleted or defined.
User Response:
See previous messages for further information. If the error persists report the problem to IBM.
MSGS0356E: Unable to define or delete Queue {0}, MQException reason code {1}
Explanation
It was not possible to delete or define the Queue.
User Response:
See previous messages for further information. If the error persists report the problem to IBM.
MSGS0357E: IOException deleting or defining Queue {0}
Explanation
It was not possible to delete or define the Queue.
User Response:
See previous messages for further information. If the error persists report the problem to IBM.
MSGS0358E: Unable to obtain list of defined Queues for PCF reason {0}
Explanation
It was not possible to obtain a list of the Queues which already exist.
User Response:
See previous messages for further information. If the error persists report the problem to IBM.
MSGS0359E: Unable to obtain list of defined Queues because there was no response from the JMS Server
Explanation
It was not possible to obtain a list of the Queues as the JMS Server did not respond.
User Response:
Check the JMS Server log for further information. If the error persists report the problem to IBM.
MSGS0360E: Unable to obtain list of defined Queues, MQException reason code {0}
Explanation
It was not possible to obtain a list of the Queues which already exist because of an MQException
User Response:
See previous messages for further information. If the error persists report the problem to IBM.
MSGS0361E: IOException obtaining list of defined Queues
Explanation
It was not possible to obtain a list of the Queues which already exist because of an IOException
User Response:
See previous messages for further information. If the error persists report the problem to IBM.
MSGS0400E: Unable to define Queue {0} on the JMS Server
Explanation
It was not possible to define the given Queue on the JMS Server. It will not therefore be usable by applications.
User Response:
See previous messages for further information. Stop and restart the JMS Server to retry.
MSGS0401E: Unable to ensure all necessary Queues are defined on the JMS Server
Explanation
It was not possible to ensure all necessary queues have been defined on the JMS Server. Some Queues may not have been defined.
User Response:
See previous messages for further information. Stop and restart the JMS Server to retry.
MSGS0450E: Unable to access the configuration for the JMS Server: {0}
Explanation
It was not possible to access the configuration for the JMS Server so it is not possible to ensure all necessary queues have been defined on the JMS Server.
User Response:
See previous messages for further information.
MSGS0451E: Unable to define Queue {0} on the JMS Server
Explanation
It was not possible to define the given Queue on the JMS Server. It will not therefore be usable by applications.
User Response:
See previous messages for further information. Stop and restart the JMS Server to retry.
MSGS0452E: Exception adding JMSQueueAdminService notification listener: {0}
Explanation
An Exception occurred when adding the JMSQueueAdminService as a notification listener so it is not possible to ensure all necessary queues have been defined on the JMS Server.
User Response:
See previous messages for further information.
MSGS0500E: The userid {0} is longer than the maximum supported userid length of {1} characters
Explanation
The userid sent to the JMS Server is longer than the maximum supported userid length. The JMS connection request is rejected.
User Response:
Use a shorter userid which is no longer than the maximum supported userid length.
MSGS0501E: The JMS Server failed to create a security service listener socket: {0}
Explanation
While initializing the JMS Server security service a problem was encountered which prevented the creation of the security service listener socket. Without the security service listener socket no authentication or authorization to JMS Server resources can be performed.
User Response:
Investigate the reason why no socket could be obtained. The problem may be caused by insufficient system or network resources.
MSGS0502E: The JMS Server security listener thread failed to accept a connection: {0}
Explanation
A problem occurred when the JMS Server security service tried to accept a connection from the internal WebSphere MQ Queue Manager or WebSphere MQ Publish Subscribe Broker. The failing request will be automatically rejected.
User Response:
Investigate the reason why a connection could not be accepted. The problem may be caused by insufficient system or network resources.
MSGS0503E: An JMS Server security service thread received an unrecognized command byte: {0}
Explanation
The JMS Server security service received an unrecognized command byte from the internal WebSphere MQ Queue Manager or WebSphere MQ Publish Subscribe Broker. The failing request will be automatically rejected.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MSGS0504E: An JMS Server security service thread experienced a socket exception: {0}
Explanation
The JMS Server security service caught a socket exception while in session with the internal WebSphere MQ Queue Manager or WebSphere MQ Publish Subscribe Broker. This may be because the peer closed the session and may not indicate a problem.
User Response:
Retry the failing operation. If the problem persists investigate the reasons as to why the socket exception is being thrown. The problem may be caused by insufficient system or network resources.
MSGS0505E: An JMS Server security service thread experienced an exception while closing a socket: {0}
Explanation
The JMS Server security service caught a socket exception while in session with the internal WebSphere MQ Queue Manager or WebSphere MQ Publish Subscribe Broker. This may be because the peer closed the session and may not indicate a problem.
User Response:
Retry the failing operation. If the problem persists investigate the reasons as to why the socket exception is being thrown. The problem may be caused by insufficient system or network resources.
MSGS0506E: An JMS Server security service thread experienced an exception while getting i/o streams from a socket: {0}
Explanation
The JMS Server security service caught a socket exception while in session with the internal WebSphere MQ Queue Manager or WebSphere MQ Publish Subscribe Broker. This may be because the peer closed the session and may not indicate a problem.
User Response:
Retry the failing operation. If the problem persists investigate the reasons as to why the socket exception is being thrown. The problem may be caused by insufficient system or network resources.
MSGS0507E: A JMS Server security service thread experienced a protocol error: {0}
Explanation
The JMS Server security service received unrecognized data from the internal WebSphere MQ Queue Manager or WebSphere MQ Publish Subscribe Broker. The failing request will be automatically rejected.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MSGS0508E: The JMS Server security service was unable to authenticate userid: {0}
Explanation
The JMS Server security service was unable to authenticate the userid because either the userid is invalid or the password was incorrect.
User Response:
Check that the userid is valid and that the password is correct.
MSGS0509E: The JMS Server security service was unable to authorize userid {0} to access resource {1} with {2} permission
Explanation
The JMS Server security service was unable to authorize the userid to the resource with the requested permission because no suitable authorization permission exists for the userid and resource.
User Response:
Check that the JMS Server authorization table includes a suitable authorization for the userid and resource.
MSGS0510E: The JMS Server security service does not support structured record {0} at version {1}
Explanation
The JMS Server security service received a structured record at a version it does not support. This may mean that the sender is at a more recent version level than the JMS Server security service.
User Response:
Check the sender version level and if necessary upgrade the JMS Server to a compatible version.
MSGS0511E: The JMS Server security service could not identify structured record {0}
Explanation
The JMS Server security service could not identify a structured record in the data it received, this may be due to data corruption.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MSGS0512E: The JMS Server security service received structured record {0} containing an unsupported flag value {1}
Explanation
The JMS Server security service received a structured record which contained a flag value that is not supported.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MSGS0550E: While parsing {0} an XML parser exception occurred: {1}
Explanation
The XML parser encountered an error while parsing the JMS Server authorizations file.
User Response:
With the help of the exception text correct the problem in the XML file causing the parsing error.
MSGS0551E: JMS Server authorization file {0} not found
Explanation
The JMS Server authorization file could not be found, no JMS Server resource authorizations are possible.
User Response:
Check that a copy of the JMS Server authorization file exists in the was_install/config/cells/
directory. MSGS0600E: An exception occurred determining the Embedded Messaging paths: {0}
Explanation
Embedded Messaging will not be usable.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MSGS0601I: WebSphere Embedded Messaging has not been installed
Explanation
WebSphere Embedded Messaging has not been installed on this node so will not be available.
User Response:
If WebSphere Embedded Messaging is to be used on this node it must be installed.
MSGS0602I: WebSphere Embedded Messaging Client only has been installed
Explanation
WebSphere Embedded Messaging Server has not been installed on this node so will not be available.
User Response:
If a JMSServer is to be started on this node, WebSphere Embedded Messaging Server must be installed.
MSGS0650I: MQJD JMS Provider open for business
Explanation
This is an informational message.
User Response:
No action required.
MSGS0651I: The MQJD JMS Provider is not installed
Explanation
The MQJD classes could not be found.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MSGS0652E: The correct MQJD JMS Provider level has not been installed
Explanation
The level of MQJD installed may is not supported by this version of WebSphere Application Server.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MSGS0653E: A Security exception occurred during MQJD JMS Provider startup: {0}
Explanation
The level of MQJD installed may not be supported by this version of WebSphere Application Server.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MSGS0654E: MQJD JMS Provider an unexpected Illegal Argument exception occurred: {0}
Explanation
The level of MQJD installed may not be supported by this version of WebSphere Application Server.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MSGS0655E: MQJD JMS Provider an unexpected exception occurred: {0}
Explanation
This is an unexpected exception. The cause can not be immediately determined.
User Response:
For further information on resolving this error, please consult support. For more information, see Get support for WebSphere Application Server for iSeries.
MSGS0656I: Starting the MQJD JMS Provider
Explanation
This is an informational message.
User Response:
No action required.
MSGS0657I: Stopping the MQJD JMS Provider
Explanation
This is an informational message.
User Response:
No action required.
MSGS0658I: MQJD JMS Provider is stopped
Explanation
This is an informational message.
User Response:
No action required.
MSGS0659E: Unable to start the MQJD JMS Provider as the Embedded Messaging Client has not been installed.
Explanation
The WebSphere Embedded Messaging Client must be installed in order to use the MQJD JMS Provider.
User Response:
Install the WebSphere Embedded Messaging Client on this node.
Explanation
If the message does not give sufficient information, check previous messages for futher help.
User Response:
See previous messages for further information.