Wso2 EI-6.6 is not compatible with Qpid-jms-client 2.0 of Azure JMS

[akAsara]

Description

Wso2 EI-6.6 is not compatible with Qpid-jms-client 2.0 of Azure JMS and observed the below exception.

[2022-07-05 14:13:32,457] ERROR {org.apache.axis2.transport.base.BaseUtils} - JNDI lookup of name SBCF returned a org.apache.qpid.jms.JmsConnectionFactory while a interface javax.jms.ConnectionFactory was expected
[2022-07-05 14:13:32,459] FATAL {org.wso2.carbon.core.init.CarbonServerManager} - WSO2 Carbon initialization Failed org.apache.axis2.transport.base.BaseTransportException: JNDI lookup of name SBCF returned a org.apache.qpid.jms.JmsConnectionFactory while a interface javax.jms.ConnectionFactory was expected
 at org.apache.axis2.transport.base.BaseUtils.handleException(BaseUtils.java:168)
 at org.apache.axis2.transport.jms.JMSUtils.lookup(JMSUtils.java:760)
 at org.apache.axis2.transport.jms.JMSConnectionFactory.initJMSConnectionFactory(JMSConnectionFactory.java:181)
 at org.apache.axis2.transport.jms.JMSConnectionFactory.<init>(JMSConnectionFactory.java:158)
 at org.apache.axis2.transport.jms.JMSConnectionFactoryManager.loadConnectionFactoryDefinitions(JMSConnectionFactoryManager.java:89)
 at org.apache.axis2.transport.jms.JMSConnectionFactoryManager.<init>(JMSConnectionFactoryManager.java:76)
 at org.apache.axis2.transport.jms.JMSSender.init(JMSSender.java:85)
 at org.apache.axis2.context.ConfigurationContextFactory.initTransportSenders(ConfigurationContextFactory.java:300)
 at org.apache.axis2.context.ConfigurationContextFactory.init(ConfigurationContextFactory.java:231)
 at org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:93)
 at org.wso2.carbon.core.CarbonConfigurationContextFactory.createNewConfigurationContext(CarbonConfigurationContextFactory.java:65)
 at org.wso2.carbon.core.init.CarbonServerManager.initializeCarbon(CarbonServerManager.java:415)
 at org.wso2.carbon.core.init.CarbonServerManager.removePendingItem(CarbonServerManager.java:305)
 at org.wso2.carbon.core.init.PreAxis2ConfigItemListener.bundleChanged(PreAxis2ConfigItemListener.java:118)
 at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:973)
 at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
 at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)

But, Qpid-jms-client 0.32 and 0.52 is working as expected without any issue. It seems, Qpid-jms-client version 2.0 is compiled using Jakarta JMS API 3.0 whereas Wso2 JMS transport is built on top of JMS API 2.0.

Steps to Reproduce

1. create a setup to connect with Azure JMS.
2. Download Qpid-jms-client and it's all the dependency jars from here[1].
3. Place them within <EI_HOME>/lib folder.
4. Start the server

[1]https://mvnrepository.com/artifact/org.apache.qpid/qpid-jms-client/2.0.0

Affected Component

MI

Version

6.6

Environment Details (with versions)

No response

Relevant Log Output

No response

Related Issues

No response

Suggested Labels

Azure JMS, Qpid-jms-client

[github-actions[bot]]

This issue is NOT closed with a proper Resolution/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Resolution/Cannot Reproduce - Issue cannot be reproduced.
      - Resolution/Duplicate - Issue is already reported before.
      - Resolution/Fixed - Issue has already been fixed.
      - Resolution/Answered - Issue has already been answered.
      - Resolution/Invalid - Issue is invalid.
      - Resolution/Not a bug - Issue is not a bug.
      - Resolution/Postponed - Issue is postponed.
      - Resolution/Won’t Fix - Issue won't be fixed.