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
Error type: JMS:ACK02Likely causes
- There was an error in the context of the acknowledgment of an inflight message.
- The session acknowledgment mode (
IMMEDIATE,AUTO,MANUALorDUPS_OK) does not match how the flow acknowledges messages.
03How to fix it
- Check which acknowledgment mode the listener or Consume operation uses.
- With
MANUALorDUPS_OK, review the flow design and 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:ACK.
04Official documentation
→Related errors
- JMS:CONSUMINGJMS: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.
- JMS:CONNECTIVITYJMS:CONNECTIVITY means the JMS connection is no longer valid, and the connector disposes of it. Check the broker and configure a reconnection strategy so the app reconnects by itself.
- Session's XAResource has not been enlisted in a distributed transactionThis ActiveMQ error appears when an XA connection or session is used outside a transaction on ActiveMQ 5.16.x and later. Run the XA work inside a transaction, or add jms.xaAckMode=1 to the broker URL.
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