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
Error type: JMS:CONSUMING02Likely 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
- Check the depth of unacknowledged messages on the broker side and review the application logic.
- Be sure that every message is acknowledged or the session recovers.
- Turn on verbose logging: in
log4j2.xmladd<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. - Handle the failure with an error handler of type
JMS:CONSUMING.
04Official documentation
→Related errors
- JMS:ACKJMS:ACK means an error happened while acknowledging an in-flight message. Review the acknowledgment mode and make sure every path through the flow either acknowledges the message or recovers the session.
- JMS:TIMEOUTJMS:TIMEOUT means the timeout for the requested JMS operation was exceeded. Check why the broker or the replying party did not answer in time before raising the timeout.
- JMS:DESTINATION_NOT_FOUNDJMS:DESTINATION_NOT_FOUND means JMS Connector could not find or create the queue or topic. Check the destination name and that the connecting user is allowed to use or create it on the broker.
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