Exception Strategy Configuration Reference
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. |
This page provides details on the elements you configure for exception strategies. This information is pulled directly from mule.xsd
and is cached. If the information appears to be out of date, refresh the page. For more information on exception strategies, see Error Handling.
Default Exception Strategy
Provides default exception handling.
Name | Description |
---|---|
|
Determines whether Type: |
|
Name of the exception strategy used in ref attribute of Type: |
|
The expression to be evaluated to determine if this exception strategy should be executed. This should always be a boolean expression. Type: |
|
Stop the flow/service when an exception occurs. Restart the flow/service manually after this (for example, using JMX). Type: |
Name | Cardinality | Description |
---|---|---|
|
0..1 |
These exceptions are considered "delivered" after handling by the exception strategy. Any exception not accepted by this filter is redelivered/rolled back. You can set a comma-separated list of wildcard patterns that’s matched against the fully qualified class name of the current exception. |
|
0..1 |
These exceptions are redelivered/rolled back after handling by the exception strategy. You can set a comma-separated list of wildcard patterns that’s matched against the fully qualified class name of the current exception. |
|
0..1 |
A message processor A placeholder for message processor elements. |
|
0..1 |
An outbound endpoint A placeholder for outbound endpoint elements. Outbound endpoints dispatch messages to the underlying transport. |
|
0..1 |
A placeholder for message processor elements. |
Custom Exception Strategy
A user-defined exception strategy.
Name | Description |
---|---|
|
Determines whether ExceptionNotifications are fired from this strategy when an exception occurs. Default is true. Type: |
|
Name of the exception strategy that’s used in ref attribute of 'exception-strategy' element. Type: |
|
The expression that’s evaluated to determine if this exception strategy should be executed. This should always be a boolean expression. Type: |
|
A class that implements the ExceptionListener interface. In addition, if an 'outbound-endpoint' element is specified, it is set as an "endpoint" bean property. Type: |
Name | Cardinality | Description |
---|---|---|
|
0..1 |
These exceptions are considered "delivered" after handling by the exception strategy. Any exception not accepted by this filter is redelivered/rolled back. You can set a comma-separated list of wildcard patterns that are matched against the fully qualified class name of the current exception. |
|
0..1 |
These exceptions are redelivered/rolled back after handling by the exception strategy. You can set a comma-separated list of wildcard patterns that is matched against the fully qualified class name of the current exception. |
|
0..1 |
A message processor A placeholder for message processor elements. |
|
0..1 |
An outbound endpoint A placeholder for outbound endpoint elements. Outbound endpoints dispatch messages to the underlying transport. |
|
0..1 |
A placeholder for message processor elements. |
|
0..* |
Spring-style property element for custom configuration. |