MuleSoft · JMS Connector

JMS:CONSUMING

Short answer

JMS:CONSUMING means an error occurred while consuming messages, and it can simply mean no message was pending. If consumption has stopped altogether, look for a backlog of unacknowledged messages on the broker.

VerifiedLast verified

01Error text

MuleSoft error
Error type: JMS:CONSUMING

02Likely causes

  • An error occurred while consuming messages. This error might relate to the absence of a pending message.
  • A large number of unacknowledged messages, usually from manual acknowledgment with incomplete ack or recover paths, can make the consumer stop.

03How to fix it

  1. Check the depth of unacknowledged messages on the broker side and review the application logic.
  2. Be sure that every message is acknowledged or the session recovers.
  3. Turn on verbose logging: in log4j2.xml add <AsyncLogger name="org.mule.extensions.jms" level="DEBUG"/> and <AsyncLogger name="org.mule.jms.commons" level="DEBUG"/>. Increase the logging level on the broker side as well.
  4. Handle the failure with an error handler of type JMS:CONSUMING.

04Official documentation

Test every fix in a non-production environment before you apply it to production. See how entries are verified.

More for MuleSoft work:Open MuleSoft jobsMuleSoft rates and salariesHire a senior MuleSoft developer

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.