Contact Us 1-800-596-4880

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.

Table 1. Attributes of <default-exception-strategy…​>
Name Type Required Default Description

enableNotifications

boolean

no

Determines whether ExceptionNotifications will be fired from this strategy when an exception occurs. Default is true.

name

name (no spaces)

no

Name of the exception strategy that will be used in ref attribute of 'exception-strategy' element

when

string

no

The expression that will be evaluated to determine if this exception strategy should be executed. This should always be a boolean expression.

stopMessageProcessing

boolean

no

false

Stop the flow/service when an exception occurs. You will need to restart the flow/service manually after this (e.g, using JMX).

Table 2. Child Elements of <default-exception-strategy…​>
Name Cardinality Description

commit-transaction

0..1

These exceptions will be considered "delivered" after handling by the exception strategy. Any exception not accepted by this filter will be redelivered/rolled back. You can set a comma-separated list of wildcard patterns that will be matched against the fully qualified class name of the current exception.

rollback-transaction

0..1

These exceptions will be redelivered/rolled back after handling by the exception strategy. You can set a comma-separated list of wildcard patterns that will be matched against the fully qualified class name of the current exception.

abstract-message-processor

0..1

A message processor A placeholder for message processor elements.

abstract-outbound-endpoint

0..1

An outbound endpoint A placeholder for outbound endpoint elements. Outbound endpoints dispatch messages to the underlying transport.

abstract-mixed-content-message-processor

0..1

A placeholder for message processor elements.

Custom exception strategy

A user-defined exception strategy.

Table 3. Attributes of <custom-exception-strategy…​>
Name Type Required Default Description

enableNotifications

boolean

no

Determines whether ExceptionNotifications will be fired from this strategy when an exception occurs. Default is true.

name

name (no spaces)

no

Name of the exception strategy that will be used in ref attribute of 'exception-strategy' element

when

string

no

The expression that will be evaluated to determine if this exception strategy should be executed. This should always be a boolean expression.

class

class name

yes

A class that implements the ExceptionListener interface. In addition, if an 'outbound-endpoint' element is specified, it is set as an "endpoint" bean property.

Table 4. Child Elements of <custom-exception-strategy…​>
Name Cardinality Description

commit-transaction

0..1

These exceptions will be considered "delivered" after handling by the exception strategy. Any exception not accepted by this filter will be redelivered/rolled back. You can set a comma-separated list of wildcard patterns that will be matched against the fully qualified class name of the current exception.

rollback-transaction

0..1

These exceptions will be redelivered/rolled back after handling by the exception strategy. You can set a comma-separated list of wildcard patterns that will be matched against the fully qualified class name of the current exception.

abstract-message-processor

0..1

A message processor A placeholder for message processor elements.

abstract-outbound-endpoint

0..1

An outbound endpoint A placeholder for outbound endpoint elements. Outbound endpoints dispatch messages to the underlying transport.

abstract-mixed-content-message-processor

0..1

A placeholder for message processor elements.

spring:property

0..*

Spring-style property element for custom configuration.