AnsweredAssumed Answered

VSE Connection To Webshpere MQ Instance

Question asked by jeff.wallace on Jun 8, 2016
Latest reply on Jun 8, 2016 by Prem_Bairoliya


One of our users has recorded some WebSphere MQ traffic.  When they deploy the .VSM file out to the VSE and start the service, it will immediately fail with the following error ::

 

========================================================
| Exception: 
============================================================================
| Message:     Error opening queue manager QM_TEST, Completion Code 2 (MQCC_FAILED), Reason Code 2059 (MQRC_Q_MGR_NOT_AVAILABLE)
----------------------------------------------------------------------------
| Trapped Exception: MQJE001: Completion Code '2', Reason '2059'.
| Trapped Message:   com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2059'.
----------------------------------------------------------------------------
STACK TRACE
com.ibm.mq.MQException: MQJE001: Completion Code '2', Reason '2059'.
...
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2059;AMQ9204: Connection to host 'win1552218(1414)' rejected. [1=com.ibm.mq.jmqi.JmqiException[CC=2;RC=2059;AMQ9205: The host name supplied is not valid. [3=win1552218,4=TCP]],3=win1552218(1414),5=RemoteTCPConnection.resolveHostname]
  at com.ibm.mq.jmqi.remote.internal.RemoteFAP.jmqiConnect(RemoteFAP.java:2072)
  at com.ibm.mq.jmqi.remote.internal.RemoteFAP.jmqiConnect(RemoteFAP.java:1286)
  at com.ibm.mq.MQSESSION.MQCONNX_j(MQSESSION.java:923)
  at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:230)
  ... 43 more
Caused by: com.ibm.mq.jmqi.JmqiException: CC=2;RC=2059;AMQ9205: The host name supplied is not valid. [3=win1552218,4=TCP]
  at com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection.resolveHostname(RemoteTCPConnection.java:400)
  at com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection.parseConnectionName(RemoteTCPConnection.java:288)
  at com.ibm.mq.jmqi.remote.internal.RemoteTCPConnection.protocolConnect(RemoteTCPConnection.java:942)
  at com.ibm.mq.jmqi.remote.internal.system.RemoteConnection.connect(RemoteConnection.java:1162)
  at com.ibm.mq.jmqi.remote.internal.system.RemoteConnectionPool.getConnection(RemoteConnectionPool.java:353)
  at com.ibm.mq.jmqi.remote.internal.RemoteFAP.jmqiConnect(RemoteFAP.java:1660)
  ... 46 more
============================================================================

 

 

All components are on individual devices.  Meaning, DevTest Workstation is on its own server, DevTest VSE is on its own server, and the WebSphere instance is on its own server.

 

We have tried defining the MQ asset with fully-qualified names yet that doesn't have any effect. 
Is there something else we have to do in order for the VSE to successfully reach out to the MQ instance?

Outcomes