Support Article

JMSListener not working due to ClassCastException

SA-29757

Summary



Th user tried to migrate from Tibco to Solace queues for their JMS service and connect. But after migration, they are getting an error.

Error Messages



Object at JNDI node 'PUB_CF' doesn't implement javax.jms.QueueConnectionFactory

2016-10-22 17:24:41,833 [ JMS-Thread-16] [ STANDARD] [ ] ( services.jms.JMSListener) ERROR .RIMMSPostResponseSolace AutoMarginCall - Caught java.lang.ClassCastException in listener RIMMSPostResponseSolace
java.lang.ClassCastException: com.solacesystems.jms.SolConnectionFactoryImpl cannot be cast to javax.jms.ConnectionFactory
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.initializeConnection(JMSListener.java:984)
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.runPoller(JMSListener.java:743)
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.run_(JMSListener.java:738)
at com.pega.pegarules.integration.engine.internal.services.listener.ServiceListenerBaseImpl.run(ServiceListenerBaseImpl.java:445)
at java.lang.Thread.run(Thread.java:662)


Steps to Reproduce



Not applicable


Root Cause



A defect or configuration issue in the operating environment.

Resolution



Make the following change to the operating environment:
There is a client imported jms.jar in the pega database table 'pr_engineclasses'. The jar is incompatible with Solace jars. Removing the records in the pr_engineclasses table related to the 'jms.jar' resolves the issue.

 

Published October 28, 2016 - Updated November 18, 2016

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.