Support Article
Message mismap error while message consumption by JMSMDB
SA-53049
Summary
A message mismap error occurs while message consumption by the JMSMDB Listener.
Error Messages
[AResourceAdapter : 1] [ STANDARD] [ ] [ ] ( services.jms.JMSListener) ERROR - Caught exception in JMS service listener myJMSMDBListener
com.pega.pegarules.pub.PRException: Expecting a MapMessage, received a message of type: com.jms.JMSTextMessage
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.readRequestData(JMSListener.java:1903) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.handleRequest(JMSListener.java:1276) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListener.runOnce(JMSListener.java:710) ~[printegrint.jar:?]
at com.pega.pegarules.integration.engine.internal.services.jms.JMSListenerServant.invoke(JMSListenerServant.java:112) ~[printegrint.jar:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact(EngineImpl.java:331) ~[prprivate.jar:?]
Steps to Reproduce
- Integrate the JMSMDB Listener through the following PDN article:
https://pdn.pega.com/deploying-jms-message-driven-bean-mdb-represents-jms-mdb-listener-pega-7 - Post a JMS message into the destination
Root Cause
A software use or operation error. Pega evaluated the posted Text Message as a Map Message. The Requested Type is set as Map Message in the Service JMS rule, by default.
Resolution
Perform the following local-change:- Reconfigure the JMS Service Request rule by changing the Request Type in the Request tab
- Restart the server
Published March 21, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.