Technote

(troubleshooting)
MQJMS2005 reason code 2059 createQueueConnection failed on starting WebSphere Commerce Server
Problem(Abstract)
You start the WebSphere Commerce Server and receive WebSphere MQ errors MQJMS2005 and reason code 2059 (MQRC_Q_MGR_NOT_AVAILABLE).
Symptom
89cb137 FreePool EJ2CA0046E: Method createManagedConnctionWithMCWrapper caught the exception, 'ResourceAllocationException,' during the creation of ManagedConnection for resource JMS$JMSQueueConnectionFactory,

Original exception: javax.resource.spi.ResourceAdapterInternalException: createQueueConnection failed at com.ibm.ejs.jms.JMSCMUtils.mapToResourceException (JMSCMUtils.java:123) at com.ibm.ejs.jms.JMSManagedQueueConnection.createConnection(JMSManagedQueueConnection.java:119)
and
Next Linked Exception: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1450)
and
Next Linked Exception: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2059 at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:172)
at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnection(MQBindingsManagedConnectionFactoryJ11.java:141)
Cause Most likely reasons for this failure:

  1. The default queue manager is not running.

  2. The MQ listener program associated with the default queue manager is not running.

  3. The default queue manager is not defined on the local system.

Diagnosing the problem The trace shows an exception when WebSphere Commerce is trying to connect to a queue manager. The reason code is 2059, MQRC_Q_MGR_NOT_AVAILABLE. The MQJMS2005 failed to create MQQueueManager for '' appears to be looking for a queue manager name that is blank. This is correct only if the queue manager created by the customer is the default queue manager. Resolving the problem The WebSphere Commerce Server JMS application is attempting to make a bindings connection to a local queue manager. Since the connection request did not include a queue manager name, the assumption is that it is a bindings connection to a default queue manager on the local machine.

There are many things that could cause this sort of failure. The following is a debugging approach for the most likely reasons for the failure.

  1. Determine the name of the queue manager.

    • The WebSphere Commerce Server admin should be able to provide the information. Assume that the queue manager name is FRED.

  2. Verify that the queue manager exists on the local machine, and that it is running.

    • Issue the following command: strmqm FRED. The 'strmqm' command will either:

      • start the queue manager

      • return a message stating that the queue manager is already started

      • return a message stating that the queue manager does not exist

  3. Verify that the listener program is running.

    • Issue the following command: runmqlsr -t tcp FRED or runmqlsr -m FRED -t tcp. The 'runmqlsr' command will either:

      • start the listener on the default port (1414)

      • return a message stating that the listener is already running

  4. Verify that FRED is the default queue manager.

    • Issue the runmqsc command without specifying a queue manager name and the program will connect to the default queue manager, assuming that one exists.

    • A subsequent display qmgr command will give you the default queue manager name.

  5. If necessary make FRED the default queue manager.

Cross Reference information
Segment Product Component Platform Version Edition
Commerce WebSphere Commerce - Express Configuration i5/OS, Linux, Windows 5.6, 5.6.1, 5.6.1.1, 5.6.1.2, 5.6.1.3, 5.6.1.4, 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4
Commerce WebSphere Commerce Professional Edition Configuration AIX, i5/OS, Linux, Solaris, Windows 5.6.1, 5.6.1.1, 5.6.1.2, 5.6.1.3, 6.0, 6.0.0.1, 6.0.0.2, 6.0.0.3, 6.0.0.4, 5.6.1.4
   

Document Information

Current web document: http://www.ibm.com/support/docview.wss?uid=swg21227679