Failed to create MQQueueManager MQJMS2005|2059
search cancel

Failed to create MQQueueManager MQJMS2005|2059

book

Article ID: 191180

calendar_today

Updated On:

Products

CA Application Performance Management Agent (APM / Wily / Introscope) CA Application Performance Management (APM / Wily / Introscope) INTROSCOPE DX Application Performance Management

Issue/Introduction

Upon the start of the IBM Integration Bus, we can see below error inside the Agent log, Investigator do not show the Queue Manager node that log is pointing, in this case the Queue Manager "S1IIBP22".

Error:

 [ERROR] [com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.MBStatisticsCleanup] MBStatisticsCleanup Cleanup error:
 [ERROR] [com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.MBStatisticsCleanup] MQJMS2005: failed to create MQQueueManager for 'S1IIBP22:AUTPRD02QM'.
javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for 'S1IIBP22:AUTPRD02QM'.
 at com.ibm.msg.client.wmq.v6.jms.internal.ConfigEnvironment.newException(ConfigEnvironment.java:402)
 at com.ibm.msg.client.wmq.v6.jms.internal.MQConnection.createQM(MQConnection.java:1484)
 at com.ibm.msg.client.wmq.v6.jms.internal.MQConnection.createQMNonXA(MQConnection.java:1541)
 at com.ibm.msg.client.wmq.v6.jms.internal.MQConnection.<init>(MQConnection.java:732)
 at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createV6ProviderConnection(WMQConnectionFactory.java:7122)
 at com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createProviderConnection(WMQConnectionFactory.java:6640)
 at com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.createConnection(JmsConnectionFactoryImpl.java:295)
 at com.ibm.mq.jms.MQConnectionFactory.createCommonConnection(MQConnectionFactory.java:6230)
 at com.ibm.mq.jms.MQConnectionFactory.createConnection(MQConnectionFactory.java:6258)
 at com.ibm.mq.jms.Cleanup.cleanup(Cleanup.java:1022)
 at com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.MBStatisticsCleanup.cleanQueue(MBStatisticsCleanup.java:396)
 at com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.MBStatisticsCleanup.doCleanup(MBStatisticsCleanup.java:362)
 at com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.v7.MBTreeConfigMain.processCleaning(MBTreeConfigMain.java:639)
 at com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.v7.MBTreeConfigMain.access$2(MBTreeConfigMain.java:606)
 at com.wily.powerpack.websphereMQ.agent.MQMonitor.MBMonitor.v7.MBTreeConfigMain$1.run(MBTreeConfigMain.java:224)
Caused by: com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2059'.
 at com.ibm.msg.client.wmq.v6.base.internal.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:236)
 at com.ibm.msg.client.wmq.v6.base.internal.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:302)
 at com.ibm.msg.client.wmq.v6.base.internal.MQClientManagedConnectionFactoryJ11.createManagedConnection(MQClientManagedConnectionFactoryJ11.java:139)
 at com.ibm.msg.client.wmq.v6.base.internal.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.java:1186)
 at com.ibm.msg.client.wmq.v6.base.internal.MQQueueManager.procure(MQQueueManager.java:1275)
 at com.ibm.msg.client.wmq.v6.base.internal.MQQueueManager.<init>(MQQueueManager.java:271)
 at com.ibm.msg.client.wmq.v6.jms.internal.MQConnection.createQM(MQConnection.java:1367)
 ... 13 more
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2059;AMQ9204: Connection to host 'S1IIBP22(1414)' rejected. [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2059;AMQ9213: A communications error for  occurred. [1=java.net.ConnectException[Connection refused (Connection refused)],3=S1IIBP22]],3=S1IIBP22(1414),5=RemoteTCPConnection.connnectUsingLocalAddress]
 at com.ibm.mq.jmqi.remote.internal.RemoteFAP.jmqiConnect(RemoteFAP.java:2010)
 at com.ibm.mq.jmqi.remote.internal.RemoteFAP.jmqiConnect(RemoteFAP.java:1227)
 at com.ibm.msg.client.wmq.v6.base.internal.MQSESSION.MQCONNX_j(MQSESSION.java:840)
 at com.ibm.msg.client.wmq.v6.base.internal.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:228)
 ... 19 more
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2059;AMQ9213: A communications error for  occurred. [1=java.net.ConnectException[Connection refused (Connection refused)],3=S1IIBP22]
 at com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection.connnectUsingLocalAddress(RemoteTCPConnection.java:663)
 at com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection.protocolConnect(RemoteTCPConnection.java:991)
 at com.ibm.mq.jmqi.remote.internal.system.RemoteConnection.connect(RemoteConnection.java:1112)
 at com.ibm.mq.jmqi.remote.internal.system.RemoteConnectionPool.getConnection(RemoteConnectionPool.java:350)
 at com.ibm.mq.jmqi.remote.internal.RemoteFAP.jmqiConnect(RemoteFAP.java:1599)
 ... 22 more
Caused by: java.net.ConnectException: Connection refused (Connection refused)
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:580)
 at java.net.Socket.connect(Socket.java:529)
 at com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection$5.run(RemoteTCPConnection.java:650)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection.connnectUsingLocalAddress(RemoteTCPConnection.java:643)
 ... 26 more

Environment

CA Application Performance Management Agent 10.7 release.

Cause

Reason code 2059 means that the queue manager is not available.

The most likely cause of the problem is that the queue manager is not running or that the queue manager listener is not running. Another possible cause is that the queue manager name that is specified on the JMS connection factory is incorrect.

Resolution

1- Ensure that the queue manager is running.
You can use the dspmq command to verify this. The status of the queue manager should be Running.

2- Check the MQ FDC files in the MQ_install_root/errors and MQ_install_root/qmgrs/queue_manager_name/errors directories to see what relevant error messages may be logged there.

3- Check that the queue manager is the default queue manager. If there is no default queue manager, then define one. This can be set in the mqs.ini file. See the WebSphere MQ System Administration Guide for more information.

4- Ensure that the queue manager has a listener running and is listening on the right port.
Start the listener program using the following command:

runmqlsr -t tcp -p <port_number> -m <qmgr_name>
Powered by Wolken Software