THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Using Error Handler combined with Exception Clause is a very powerful combination. We encourage end-users to use this combination in your error handling strategies. See samples and Exception Clause.
...
...
Related to error handling is the Try Catch Finally as DSL you can use directly in your route. Its basically a mimic of the regular try catch finally in the Java language but with more power.
...
You can configure the default dead letter endpoint to use:Wiki Markup
...
...
or also from Camel 2.3.0:
...
...
The LoggingErrorHandler
The logging error handler will log (by default at ERROR level) whenever an uncaught exception is thrown. The logging category, logger and level may all be defined in the builder.
...
...
or in Spring DSL:
...
...
or also from Camel 2.3.0:
...
...
This would create an error handler which logs exceptions using the category mylogger.name and uses the level INFO for all log messages created.
...
...
Loggers may also be defined for specific routes.
...
The no error handler is to be used for disabling error handling.
...
...
or in Spring DSL:
...
...
or also from Camel 2.3.0:
...
...
TransactionErrorHandler
The TransactionErrorHandler is the default error handler in Camel for transacted routes.
...
...
If you have marked a route as transacted using the transacted DSL then Camel will automatic use a TransactionErrorHandler. It will try to lookup the global/per route configured error handler and use it if its a TransactionErrorHandlerBuilder instance. If not Camel will automatic create a temporary TransactionErrorHandler that overrules the default error handler. This is convention over configuration.
Features Support by Various Error Handlers
...
See Exception Clause documentation for documentation of some of the features above.
...
The following example shows how you can register a global error handler (in this case using the logging handler)Wiki Markup seda:aWiki Markup
Spring Based Configuration
...
...
The error handler is configured a bit differently in Java DSL and Spring DSL. Spring DSL relies more on standard Spring bean configuration whereas Java DSL uses fluent builders.
The error handler can be configured as a spring bean and scoped in:
...
The error handler is configured with the errorHandlerRef attribute.
...
...
The error handlers is inherited, so if you only have set a global error handler then its use everywhere. But you can override this in a route and use another error handler.
Spring Based Configuration Sample
In this sample we configure a Dead Letter Channel on the route that should redeliver at most 3 times and use a little delay before retrying.
First, we configure the reference to myDeadLetterErrorHandler using the errorHandlerRef attribute on the route tag.Wiki Markup myDeadLetterErrorHandler that is our Dead Letter Channel. This configuration is standard Spring using the bean element.
Finally, we have another spring bean for the redelivery policy where we can configure the options for how many times to redeliver, delays etc.Wiki Markup Wiki Markup
Using the TransactionalErrorHandler
...