Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Message mismap error while message consumption by JMSMDB



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 Expecting a MapMessage, received a message of type: com.jms.JMSTextMessage
at ~[printegrint.jar:?]
at ~[printegrint.jar:?]
at ~[printegrint.jar:?]
at ~[printegrint.jar:?]
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._invokeEngine_privact( ~[prprivate.jar:?]

Steps to Reproduce

  1. Integrate the JMSMDB Listener through the following PDN article:
  2. 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.


Perform the following local-change:
  1. Reconfigure the JMS Service Request rule by changing the Request Type in the Request tab
  2. Restart the server

Published March 21, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us