Contact Us 1-800-596-4880
  1. Homepage
  2. Mule Runtime (3.6)
  3. Developing
  4. Error Handling

  5. Reference Exception Strategy

Reference Exception Strategy

Mule Runtime Engine versions 3.5, 3.6, and 3.7 reached End of Life on or before January 25, 2020. For more information, contact your Customer Success Manager to determine how you can migrate to the latest Mule version.

You can create one or more global exception strategies to reuse in flows throughout your entire Mule application. First, create a global exception strategy, then add a Reference Exception Strategy to a flow to apply the error handling behavior of a specific global exception strategy.

When to Use

Use a reference exception strategy to instruct a flow to employ the error handling behavior defined by a global rollback exception strategy. In other words, you must ask your flow to refer to a global exception strategy for instructions on how to handle errors.

Applying a Global Rollback Exception Strategy to a Flow

Studio Visual Editor

  1. If you have not already done so, create a global catch, rollback, or choice exception strategy to which your reference exception strategy can refer.

  2. From the Error Handling palette group, drag and drop the reference exception strategy icon into the footer bar of a flow.

    reference+exception+1

  3. Open the Reference Exception Strategy’s Properties Editor, use the drop-down to reference the global catch exception strategy (below), then click anywhere on the canvas to save.

    reference+exception+2
    You can append a Reference Exception Strategy to any number of flows in your Mule application and instruct them to refer to any of the global catch, rollback or choice exception strategies you have created. You can direct any number of reference exception strategies to refer to the same global exception strategy.

Studio XML Editor or Standalone

  1. To your flow, below all the message processors, add an exception-strategy element.

  2. To the exception-strategy element, add attributes according to the table below. Refer to code below.

Attribute Value

ref

Name of the global catch-exception-strategy in your project.

doc:name

Unique name for the exception strategy, if you wish. (Not required in Standalone.)

 
<catch-exception-strategy name="Catch_Exception_Strategy">
    <logger message="#[payload]" level="INFO" doc:name="Logger"/>
</catch-exception-strategy>
<http:listener-config name="Http_Listener_Configuration" host="localhost" port="8081" doc:name="HTTP Listener Configuration"/>

<flow name="Creation1Flow1" doc:name="Creation1Flow1">
    <http:listener config-ref="Http_Listener_Configuration" path="getSomething" allowedMethods="GET" doc:name="Retrieve person">
        <http:error-response-builder statusCode="#[errorStatusCode]" reasonPhrase="#[errorReasonPhrase]"/>
    </http:listener>
    <cxf:jaxws-service doc:name="SOAP"/>
...
    <exception-strategy ref="Catch_Exception_Strategy" doc:name="Reference Exception Strategy"/>
</flow>
You can append a Reference Exception Strategy to any number of flows in your Mule application and instruct them to refer to any of the global catch, rollback or choice exception strategies you have created. You can direct any number of reference exception strategies to refer to the same global exception strategy.

See Also