What is the meaning of the timeout attribute of the XA transaction, and what happens after the timeout expires?

An XA transaction Is being configured that involves a JMS connector listening for Incoming JMS messages.

What is the meaning of the timeout attribute of the XA transaction, and what happens after the timeout expires?
A . The time that is allowed to pass between committing the transaction and the completion of the Mule flow After the timeout, flow processing triggers an error
B . The time that Is allowed to pass between receiving JMS messages on the same JMS connection After the timeout, a new JMS connection Is established
C . The time that Is allowed to pass without the transaction being ended explicitly After the timeout, the transaction Is forcefully rolled-back
D . The time that Is allowed to pass for state JMS consumer threads to be destroyed After the timeout, a new JMS consumer thread is created

Answer: C

Explanation:

* Setting a transaction timeout for the Bitronix transaction manager

● Set the transaction timeout either

C In wrapper.conf

C In CloudHub in the Properties tab of the Mule application deployment

● The default is 60 secs. It is defined as

mule.bitronix.transactiontimeout = 120

* This property defines the timeout for each transaction created for this manager.

If the transaction has not terminated before the timeout expires it will be automatically rolled

back.

———————————————————————————————————————

Additional Info around Transaction Management:

Bitronix is available as the XA transaction manager for Mule applications

● To use Bitronix, declare it as a global configuration element in the Mule application <bti:transaction-manager />

● Each Mule runtime can have only one instance of a Bitronix transaction manager, which is shared by all Mule applications

● For customer-hosted deployments, define the XA transaction manager in a Mule domain

C Then share this global element among all Mule applications in the Mule runtime