WebSphere Application Server V5 Message Listener Ports fail to start with WMSG0019E and MQJMS2008 errors
 Technote (troubleshooting)
 
Problem(Abstract)
The SystemOut.log of the IBM® WebSphere® Application Server shows the following messages output for each listener port that cannot start:

[4/11/05 19:22:32:930 GMT] 6718678f MDBListenerIm W WMSG0019E: Unable to
start MDB Listener myMessageDrivenBean, JMSDestination jms/myQueue :
javax.jms.JMSException: MQJMS2008: failed to open MQ queue
...
---- Begin backtrace for Nested Throwables
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2085


This occurs for listener ports that are configured with JMS destinations that are defined for the WebSphere JMS Provider (Embedded Messaging).
 
Cause
The problem occurs because the queue that the listener port is attempting to access has not been defined on the Embedded Messaging queue manager.

The MQ return code 2085 indicates the following:

$ mqrc 2085

2085 0x00000825 MQRC_UNKNOWN_OBJECT_NAME

 
Resolving the problem
To resolve the problem, the queue must be defined on the Embedded Messaging queue manager.

The name of the queue hosted on the Embedded Messaging queue manager must have the same administrative name that was given on the WebSphere JMS Provider Queue Destination configuration.

To determine the name of the queue follow this path in the Administrative Console:

Resources -> WebSphere JMS Provider -> WebSphere Queue Destinations -> <queue_destination_name> ->

In this example, the name of the queue which needs to be defined is "myQueue". This name was taken from the "Name" field.

The next step is to define this queue on the queue manager:

For a stand-alone BASE installation, follow this path:

Servers -> Application Servers -> <server_name> -> Server Components -> JMS Servers -> Queue names ->

For a federated Network Deployment environment, follow this path:

Servers -> JMS Servers -> jmsserver -> Queue names ->


In the "Queue names" field, add the queue which is to be hosted by this JMS Server. In this example, "myQueue" was added.
Click OK and then save and synchronize the changes.

Now, the listener port for the Application server should start successfully. Note, if there are multiple listener ports defined, you must add the queues for each listener port to the configuration of the JMS Server.

 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Java Message Service (JMS)
Operating system(s): AIX
Software version: 5.1.1
Software edition:
Reference #: 1205271
IBM Group: Software Group
Modified date: Feb 26, 2007