Single-resource and XA transactions in Mule
Choose Single Resource or XA transactions from the resources and configurations involved, set transactional actions on sources, Try scopes and operations, configure XA on JMS, Database and VM with a transaction manager, and predict how error handlers and scopes change commit, rollback and threading inside a transaction.
Design Mule applications and integration solutions using local and XA transactions for all Mule connectors that support them.
~7 min read · 5 practice questions
What the exam expects
- Choose Single Resource or XA from the connectors and global configurations that must commit together.
- Set the transactional action on a source, a Try scope or an operation, and know which component can begin a transaction.
- Configure XA for JMS, Database and VM, with a transaction manager that can recover interrupted two-phase commits.
- Predict commit or rollback from the error handler type and the component that began the transaction.
- Recognize how Async, Parallel For Each, Scatter-Gather and Flow Reference behave inside a transaction.
Single Resource (local) transaction: a transaction over one resource, such as a JMS broker, VM queues or a JDBC connection. XA transaction: a global transaction that groups operations from several transactional resources with two-phase commit (2PC). Transactional action: the transactionalAction setting that says whether a component begins, joins or ignores a transaction. Transaction manager: the component that coordinates the prepare and commit phases across XA resources (Single Resource Transactions, XA Transactions, Transaction Management).
Key facts
- Detail
- Single Resource (Local).
- Detail
- Event sources and the Try scope only.
- Detail
- Same connector, same
config-ref.
- Detail
- XA only.
- Detail
30000ms default;defaultTransactionTimeout.
- Detail
mule.bitronix.transactiontimeout, 60 seconds.
- Detail
- JMS, IBM MQ, VM, Database.
- Detail
- Dedicated XA connection type; Mule 4.10.0 or later, newer than the Spring '24 baseline.
- Detail
- Transaction stays active and can commit.
- Detail
- Runs outside it; no rollback on its errors.
Sources for this section (5)
- Transaction Managementdocs.mulesoft.com (opens in a new tab)
- Single Resource Transactionsdocs.mulesoft.com (opens in a new tab)
- Using Bitronix to Manage Transactionsdocs.mulesoft.com (opens in a new tab)
- XA Transactionsdocs.mulesoft.com (opens in a new tab)
- Configuring XA Transactions in JMS Connectordocs.mulesoft.com (opens in a new tab)
- Why does a transaction manager need a recovery process for XA transactions?
- When does Mule run XA transaction recovery?
- Why must
mule.bitronix.serverIddiffer between Mule instances? - What unit and default does
mule.bitronix.transactiontimeoutuse?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Platform Integration Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 40 lessons of the MuleSoft Platform Integration Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (5 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both