cancel
Showing results for 
Search instead for 
Did you mean: 

Connecting different versions of MQ Ibm Websphere using PI 7.1

Former Member
0 Kudos

Hi Experts,

We are having one mq server which is installed on a third party system which we are currenlty using without having any issues.

the mq series is ibm websphere version 6.

we have these following jar files installed on pi.

<jars>

<jar-name>lib/com.sap.aii.adapter.lib_api.jar</jar-name>

<jar-name>lib/ojdbc14.jar</jar-name>

<jar-name>lib/client.jar</jar-name>

<jar-name>lib/msbase.jar</jar-name>

<jar-name>lib/mssqlserver.jar</jar-name>

<jar-name>lib/msutil.jar</jar-name>

<jar-name>lib/com.ibm.mq.jar</jar-name>

<jar-name>lib/com.ibm.mqjms.jar</jar-name>

<jar-name>lib/connector.jar</jar-name>

<jar-name>lib/CL3Export.jar</jar-name>

<jar-name>lib/CL3Nonexport.jar</jar-name>

<jar-name>lib/dhbcore.jar</jar-name>

<jar-name>lib/rmm.jar</jar-name>

</jars>

we are able to connect to this system sucessfully using jms.

the issue we are facing now is we have now another new mq server installed which we want to use

this is version ibm websphere 5.3.

we have gone through sap notes and found that these jar files need to be in place for 5.3

MQSeries 5.3

  • com.ibm.mq.jar

  • com.ibm.mqbind.jar

  • com.ibm.mqjms.jar

  • connector.jar (this file can also be retrieved from the SAP J2EE server directory)

by comparing with the jar files we currenlty have installed

this jar file is missing com.ibm.mqbind.jar for 5.3

we are unable to connect to this new mq server and facing the issues.(reciever jms)

the message in rwb is

Error creating JMS connection. JMS provider gave error message as MQJMS2005: failed to create MQQueueManager for 'Servername:Queuemangername' MQJE001: An MQException occurred: Completion Code 2, Reason 2009

MQJE016: MQ queue manager closed channel immediately during connect

Closure reason = 2009, and error code as MQJMS2005.

we have gone through notes 1086303 and found that it might be due to wrong queuemanager name.

our mq team is saying that they have configured everything perfectly.

what we have is now 2 queries:

1. is this error caused due to the mqbind jar file missing.if so than we can tell our nw team to install that jar files.is it necessary as we have already jar files for version 6? will version 6 jar files be compatible if we install these new jar file which is missing as we dont want to mess the existing scenarios?

2. is there any other config we are missing on pi side so that we are 100 percent sure its not the error on pi side and some config is missing on jms side.

please advice.

many thanks.

regards

j

Accepted Solutions (0)

Answers (2)

Answers (2)

JoelTrinidade
Active Contributor
0 Kudos

Hi Jyoti,

I think i found the exact solution:

Error Message: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '<Host>:<QueueManagerName>'

...

com.ibm.mq.MQException: MQJE001: An MQException occurred: Completion Code 2, Reason 2009

MQJE016: MQ queue manager closed channel immediately during connect

Closure reason = 2009

Tip: This usually indicates that your channel name was incorrect of that you did not specify a channel of type SVRCONNN (server connection) in the channel field on your JMS channel configuration.

Source: http://www.saptechies.com/xi-jms-adapter-and-ibm-websphere-mq-faq/

regards

joel

JoelTrinidade
Active Contributor
0 Kudos

Hi Jyoti,

You say to choose between the possibility of a missing jar and other of a Queue manager. I think first and foremost get the missing jar file installed and secondly , try the following suggestions.

1) It appears that the MQ JMS server is refusing connections from the MQ JMS c=

lient. I suggest looking up "MQJMS2005" in the IBM documentation and also =

checking if the IBM specific connection string '147.149.178.44:BT.QM.IVASCT=

G' is correct.

2) I guess so because 2009 indicates a communication problem. It appears that the foreign JMS provider is restricting the number of conne=

ctions that can be made to it. I'd check the license restrictions/configura=

tion of the foreign JMS provider and ensure it allows the required number o=

f concurrent connections. The closure reason code 2009 should indicate what=

the problem is.

Regards

joel