MuleSoft · JMS Connector

Session's XAResource has not been enlisted in a distributed transaction

Short answer

This 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.

VerifiedLast verified

01Error text

MuleSoft error
javax.jms.JMSException: Session's XAResource has not been enlisted in a distributed transaction.

02Likely causes

  • ActiveMQ 5.16.x or later is used with an XA connection or XA session outside a transaction.

03How to fix it

  1. Run the XA-enabled operations inside a transaction.
  2. Or add the query parameter jms.xaAckMode=1 to the broker URL, for example vm://localhost?jms.xaAckMode=1.
  3. With ActiveMQ 5.16.x, use ActiveMQ driver 5.16.4 or later.

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.