JMSWMQ0018: Connection to Queue Manager ' QMGR ' failed with connection as ' Bindings '

Previously written a Java program that listens to MQ with JMS, calls local MQ together as normal. Today, however, the sudden call to the queue on the remote server was an error.

The following is an error message

Exception in thread "main" org.springframework.jms.UncategorizedJmsException:Uncategorized Exception occured during JMS processing; Nested exception is com.ibm.msg.client.jms.DetailedJMSException:JMSWMQ0018: Connection to Queue Manager ' BLQMGR2 ' failed with connection as ' Bindings ', The host name is ' 192.168.100.104 (1414) '.
Check that the queue Manager is started, and if it is running as a client, check to see if a listener is running. See the linked exception for more information.; Nested exception is Com.ibm.mq.MQException:JMSCMQ0001:WebSphere MQ call failed with completion code ' 2 ' (' mqcc_failed ') because ' 2058 ' (' mqrc_q ' _mgr_name_error ').
At Org.springframework.jms.support.JmsUtils.convertJmsAccessException (jmsutils.java:316)
At Org.springframework.jms.support.JmsAccessor.convertJmsAccessException (jmsaccessor.java:169)
At Org.springframework.jms.core.JmsTemplate.execute (jmstemplate.java:496)
At org.springframework.jms.core.JmsTemplate.receiveSelected (jmstemplate.java:753)
At Org.springframework.jms.core.JmsTemplate.receive (jmstemplate.java:732)
At Org.springframework.jms.core.JmsTemplate.receive (jmstemplate.java:723)
At Com.mq.test.TestReceive.showResult (testreceive.java:42)
At Com.mq.test.TestReceive.main (testreceive.java:104)
Caused by:com.ibm.msg.client.jms.DetailedJMSException:JMSWMQ0018: Connection to Queue Manager ' BLQMGR2 ' failed with connection as ' Bindings ', host name ' 192.168.100.104 (1414) '.
Check that the queue Manager is started, and if it is running as a client, check to see if a listener is running. See the linked exception for more information.
At Com.ibm.msg.client.wmq.common.internal.Reason.reasonToException (reason.java:585)
At Com.ibm.msg.client.wmq.common.internal.Reason.createException (reason.java:221)
At Com.ibm.msg.client.wmq.internal.wmqconnection.<init> (wmqconnection.java:425)
At Com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createV7ProviderConnection (Wmqconnectionfactory.java : 6902)
At Com.ibm.msg.client.wmq.factories.WMQConnectionFactory.createProviderConnection (Wmqconnectionfactory.java : 6277)
At Com.ibm.msg.client.jms.admin.JmsConnectionFactoryImpl.createConnection (jmsconnectionfactoryimpl.java:285)
At Com.ibm.mq.jms.MQConnectionFactory.createCommonConnection (mqconnectionfactory.java:6233)
At Com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection (mqqueueconnectionfactory.java:120)
At Com.ibm.mq.jms.MQQueueConnectionFactory.createConnection (mqqueueconnectionfactory.java:203)
At Org.springframework.jms.support.JmsAccessor.createConnection (jmsaccessor.java:180)
At Org.springframework.jms.core.JmsTemplate.execute (jmstemplate.java:483)
... 5 more
Caused By:com.ibm.mq.MQException:JMSCMQ0001:WebSphere MQ call failed with the completion code ' 2 ' (' mqcc_failed ') for the reason ' 2058 ' (' Mqrc_q_mgr_name _error ').
At Com.ibm.msg.client.wmq.common.internal.Reason.createException (reason.java:209)
... More

Carefully check the configuration IP address, channel, Queue Manager name, the queue is not written wrong ah, change to connect to local is also possible.

In addition, the server-side channel authentication is also disabled. Or not, finally tangled up a morning or asked the big God in the group the original connection mode TransportType not the default is 0 remote call to change to 1 (TCP) connection, see Configuration diagram.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

JMSWMQ0018: Connection to Queue Manager ' QMGR ' failed with connection as ' Bindings '