Besides using Try scope, what can begin a transaction in Mule?

• A. A transactional connector acting as an event source (Database, JMS, VM)
• B. Try scope
• C. On Error Continue Scope
• D. Raise-error

Answer: (A)

In Mule, a transaction boundary can be started by inbound resources that are configured to begin a transaction when data is received. A transactional connector acting as an event source—such as a Database inbound endpoint, a JMS listener, or a VM endpoint—starts a transaction for the processing of each message. Everything inside that inbound processing participates in that same transactional boundary until it’s committed or rolled back.

Try scope is for catching exceptions inside the flow; it does not start or establish a transaction. Likewise, On Error Continue Scope and Raise-error are error-handling constructs to respond to failures, not to create transactional boundaries.

So, a transactional connector acting as an event source is what can begin a transaction besides using Try scope.