THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Some current implementations include
- DefaultErrorHandler is the default error handler in Camel 2.0 onwards. This error handler does not support a deal letter queue, it will propagate exceptions back to the caller, as if there where no error handler at all. It has a limited set of features.
- Dead Letter Channel which supports attempting to redeliver the message exchange a number of times before sending it to a dead letter endpoint
- LoggingErrorHandler for just catching and logging exceptions
- NoErrorHandler for no error handling
- Transaction for transactional error handling (Spring based). See the Transactional Client EIP pattern.
| Info | ||
|---|---|---|
| ||
In Camel 2.0 onwards there default error handler is changed from Dead Letter Channel to DefaultErrorHandler. This error handler does not support a dead letter queue and will return exceptions back to the caller. This is what you expects when working with regular Java that exceptions will be thrown back to the caller. This error handler supports a limited set of features. |
| Tip | ||
|---|---|---|
| ||
For introduction and background material see Error handling in Camel. |
...
Short Summary of the provided Error Handlers
Default Error Handler (Dead Letter Channel)
DefaultErrorHandler new in Camel 2.0
The DefaultErrorHandler is the new default error handler in Camel 2.0. It only supports a limited set of features such as catching exception and using the Exception Clause. It does not support redelivery, delays or the likes. It will propagate exceptions back to the original caller. It does not have any dead letter queue.
Dead Letter Channel
The Dead Letter Channel is the default error handler in Camel 1.x, The default error handler is the Dead Letter Channel which is automatically configured for you. By default Camel will redeliver at most 6 times using 1 second delay, and if the exchange failed it will be logged at ERROR level.
...