What determines whether Mule uses a single-resource TX or a global XA TX?

What determines whether Mule uses a single-resource TX or a global XA TX?

• A. Number of databases in the try scope
• B. Number of JMS connectors
• C. The flow name
• D. The runtime version

Answer: (A)

In Mule, the way a flow’s transaction is handled depends on how many transactional resources participate inside the transactional boundary defined by a try scope. If you have only a single transactional resource, such as one database, the flow uses a local, single-resource transaction. But if you include more than one transactional resource within that same try scope, Mule must coordinate across them, which requires a global XA transaction to ensure atomicity across all resources. That’s why the number of databases in the try scope is the best indicator here: one database means a single-resource transaction, while multiple databases means a distributed XA transaction. The other factors listed don’t determine the transaction mode themselves; they don’t by themselves switch you from a single-resource TX to a global XA TX.

In Mule, the way a flow’s transaction is handled depends on how many transactional resources participate inside the transactional boundary defined by a try scope. If you have only a single transactional resource, such as one database, the flow uses a local, single-resource transaction. But if you include more than one transactional resource within that same try scope, Mule must coordinate across them, which requires a global XA transaction to ensure atomicity across all resources.

That’s why the number of databases in the try scope is the best indicator here: one database means a single-resource transaction, while multiple databases means a distributed XA transaction. The other factors listed don’t determine the transaction mode themselves; they don’t by themselves switch you from a single-resource TX to a global XA TX.