MuleSoft · JMS Connector

JMS:ACK

Short answer

JMS: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.

VerifiedLast verified

01Error text

MuleSoft error
Error type: JMS:ACK

02Likely causes

  • There was an error in the context of the acknowledgment of an inflight message.
  • The session acknowledgment mode (IMMEDIATE, AUTO, MANUAL or DUPS_OK) does not match how the flow acknowledges messages.

03How to fix it

  1. Check which acknowledgment mode the listener or Consume operation uses.
  2. With MANUAL or DUPS_OK, review the flow design and 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:ACK.

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.