Monday, April 18, 2011

JMS Error - JNDI lookup of name QueueConnectionFactory returned a x.y.z while a interface javax.jms.ConnectionFactory was expected

If you happen to experience this error when working with any WSO2 product you can resolve it by removing the geronimo-jms_1.1_spec-1.1.0.VERSION.jar from $CARBON_HOME/repository/components/lib. This occurs due the availability of multiple implementation of javax.jms.* in the system classpath. You'll notice the following familiar stack trace.


Caused by: org.apache.axis2.transport.base.BaseTransportException: JNDI lookup of name QueueConnectionFactory returned a org.apache.qpid.client.AMQConnectionFactory while a interface javax.jms.ConnectionFactory was expected
at org.apache.axis2.transport.base.BaseUtils.handleException(BaseUtils.java:166)
at org.apache.axis2.transport.jms.JMSUtils.lookup(JMSUtils.java:522)
at org.apache.axis2.transport.jms.JMSConnectionFactory.(JMSConnectionFactory.java:92)
at org.apache.axis2.transport.jms.JMSConnectionFactoryManager.loadConnectionFactoryDefinitions(JMSConnectionFactoryManager.java:58)
at org.apache.axis2.transport.jms.JMSConnectionFactoryManager.(JMSConnectionFactoryManager.java:45)
at org.apache.axis2.transport.jms.JMSListener.doInit(JMSListener.java:58)
at org.apache.axis2.transport.base.AbstractTransportListenerEx.init(AbstractTransportListenerEx.java:62)
at org.wso2.carbon.core.transports.AbstractTransportService.updateGlobalTransportParameters(AbstractTransportService.java:129)
... 41 more



This issue can occur if you are trying any product using with the JMS transport.

0 comments:

Post a Comment