cancel
Showing results for 
Search instead for 
Did you mean: 

error when connecting to websphere MQ from PI 7.3 using jms

Former Member
0 Kudos

Hi,

We are getting error in a sender jms channel of PI 7.3 when connecting to MQ

A channel error occurred. Detailed error (if any) : java.lang.ClassCastException: class com.ibm.mq.jms.MQQueueConnectionFactory:library:com.sap.aii.adapter.lib@com.sap.engine.boot.loader.ResourceMultiParentClassLoader@6fb916fe@alive incompatible with interface javax.jms.TopicConnectionFactory:library:jms_api@com.sap.engine.boot.loader.ResourceMultiParentClassLoader@5cdeb323@alive<br> at com.sap.aii.adapter.jms.core.connector.ConnectorImpl.getTopicCF(ConnectorImpl.java:498).


This connection was working 2 weeks back. But now it is not working. We applied note 1751177 for this error but that did not help. However, receiver jms channel is working fine.


Kindly help in this regard.


Ankit

Accepted Solutions (0)

Answers (1)

Answers (1)

Harish
Active Contributor
0 Kudos

Hi Ankit,

which MQ client library version is deployed 7.1 or 7.5?

Please check the below discussion

Regards,

Harish

Former Member
0 Kudos

MQ is 7.0. same version is deployed too. receiver channel is working fine. sender is not working.

Harish
Active Contributor
0 Kudos

Hi Ankit,

Please check the below jars if they deployed.

CL3Export.jar

CL3Nonexport.jar

dhbcore.jar

rmm.jar

connector.jar

fscontext.jar

providerutil.jar

com.ibm.mqjms.jar

com.ibm.mq.headers.jar

com.ibm.mq.jar

com.ibm.mq.jmqi.jar

com.ibm.mq.pcf.jar

reference link -

Regards,

Harish

Former Member
0 Kudos

Yes. those are present too.

Harish
Active Contributor
0 Kudos

Hi Ankit,

The error is incompatability of your MQ java Jars with PI jars. i think you need to check if there is problem in error in deploying the sap note.

Regards,

Harish

Former Member
0 Kudos

This error was coming before i deployed sap note. SAP note didnt solve the issue. It was working fine two weeks back. Suddenly it is not working. Nothing was changed from PI side. Also, if jar files are wrong, receiver jms should not work. But that is working fine.