Error Handler
来源:互联网 发布:虎扑认证的淘宝店 编辑:程序博客网 时间:2024/04/29 21:21
http://camel.apache.org/error-handler.html
Error Handler
Camel supports pluggable ErrorHandler strategies to deal with errors processing an Event Driven Consumer. An alternative is to specify the error handling directly in theDSL using theException Clause.
For introduction and background material see Error handling in Camel.
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 andException 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.
The current implementations Camel provides out of the box are:
Non transacted
- DefaultErrorHandler is the default error handler in Camel. This error handler does not support a dead 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
Transacted
- TransactionErrorHandler is the default error handler in Camel for transacted routes. See theTransactional Client EIP pattern.
These error handlers can be applied in the DSL to an entire set of rules or a specific routing rule as we show in the next examples. Error handling rules are inherited on each routing rule within a singleRouteBuilder
Short Summary of the provided Error Handlers
DefaultErrorHandler
The DefaultErrorHandler is the default error handler in Camel. Unlike Dead Letter Channel it does not have any dead letter queue, and do not handle exceptions by default.
Dead Letter Channel
The Dead Letter Channel will redeliver at most 6 times using 1 second delay, and if the exchange failed it will be logged at ERROR level.
You can configure the default dead letter endpoint to use:
RouteBuilder builder = new RouteBuilder() { public void configure() { // using dead letter channel with a seda queue for errors errorHandler(deadLetterChannel("seda:errors")); // here is our route from("seda:a").to("seda:b"); }};
or in Spring DSL
<bean id="deadLetterErrorHandler" class="org.apache.camel.builder.DeadLetterChannelBuilder"> <property name="deadLetterUri" value="log:dead"/></bean><camelContext errorHandlerRef="deadLetterErrorHandler" xmlns="http://camel.apache.org/schema/spring"> ...</camelContext>
or also from Camel 2.3.0 onwards
<camel:errorHandler id="deadLetterErrorHandler" type="DeadLetterChannel" deadLetterUri="log:dead"><camel:camelContext errorHandlerRef="deadLetterErrorHandler"> ...</camel:camelContext>
Logging Error Handler
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.
errorHandler(loggingErrorHandler("mylogger.name").level(LoggingLevel.INFO));
or in Spring DSL
<bean id="loggingErrorHandler" class="org.apache.camel.builder.LoggingErrorHandler"> <property name="logName" value="mylogger.name"/> <property name="level" value="DEBUG"/></bean><camelContext errorHandlerRef="loggingErrorHandler" xmlns="http://camel.apache.org/schema/spring"> ...</camelContext>
or also from Camel 2.3.0 onwards
<camel:errorHandler id="loggingErrorHandler" type="LoggingErrorHandler" logName="mylogger.name" level="DEBUG"/><camel:camelContext errorHandlerRef="loggingErrorHandler"> ...</camel:camelContext>
This would create an error handler which logs exceptions using the category mylogger.name and uses the level INFO for all log messages created.
from("seda:a").errorHandler(loggingErrorHandler("mylogger.name").level(LoggingLevel.DEBUG)).to("seda:b");
Loggers may also be defined for specific routes.
No Error Handler
The no error handler is to be used for disabling error handling.
errorHandler(noErrorHandler());
or in Spring DSL
<bean id="noErrorHandler" class="org.apache.camel.builder.NoErrorHandlerBuilder"/><camelContext errorHandlerRef="noErrorHandler" xmlns="http://camel.apache.org/schema/spring"> ...</camelContext>
or also from Camel 2.3.0 onwards
<camel:errorHandler id="noErrorHandler" type="NoErrorHandler"/><camel:camelContext errorHandlerRef="noErrorHandler"> ...</camel:camelContext>
TransactionErrorHandler
The TransactionErrorHandler is the default error handler in Camel for transacted routes.
Features support by variousError Handlers
Here is a breakdown of which features is supported by the Error Handler(s):
See Exception Clause documentation for documentation of some of the features above.
Scopes
The error handler is scoped as either
- global
- per route
The following example shows how you can register a global error handler (in this case using the logging handler)
RouteBuilder builder = new RouteBuilder() { public void configure() { // use logging error handler errorHandler(loggingErrorHandler("com.mycompany.foo")); // here is our regular route from("seda:a").to("seda:b"); }};
The following example shows how you can register a route specific error handler; the customized logging handler is only registered for the route fromEndpointseda:a
RouteBuilder builder = new RouteBuilder() { public void configure() { // this route is using a nested logging error handler from("seda:a") // here we configure the logging error handler .errorHandler(loggingErrorHandler("com.mycompany.foo")) // and we continue with the routing here .to("seda:b"); // this route will use the default error handler (DeadLetterChannel) from("seda:b").to("seda:c"); }};
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:
- global (the camelContext tag)
- per route (the route tag)
- or per policy (the policy/transacted tag)
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 theerrorHandlerRef attribute on the route tag.
<camelContext xmlns="http://camel.apache.org/schema/spring"> <template id="myTemplate"/><!-- set the errorHandlerRef to our DeadLetterChannel, this applies for this route only --> <route errorHandlerRef="myDeadLetterErrorHandler"> <from uri="direct:in"/> <process ref="myFailureProcessor"/> <to uri="mock:result"/> </route> </camelContext>
Then we configure myDeadLetterErrorHandler that is our Dead Letter Channel. This configuration is standard Spring using the bean element.
And finally we have another spring bean for the redelivery policy where we can configure the options for how many times to redeliver, delays etc.
<!-- here we configure our DeadLetterChannel --><bean id="myDeadLetterErrorHandler" class="org.apache.camel.builder.DeadLetterChannelBuilder"> <!-- exchanges is routed to mock:dead in cased redelivery failed --> <property name="deadLetterUri" value="mock:dead"/><!-- reference the redelivery policy to use --> <property name="redeliveryPolicy" ref="myRedeliveryPolicyConfig"/> </bean> <!-- here we set the redelivery settings --><bean id="myRedeliveryPolicyConfig" class="org.apache.camel.processor.RedeliveryPolicy"> <!-- try redelivery at most 3 times, after that the exchange is dead and its routed to the mock:dead endpoint --> <property name="maximumRedeliveries" value="3"/><!-- delay 250ms before redelivery --> <property name="redeliveryDelay" value="250"/> </bean>
From Camel 2.3.0, camel provides a customer bean configuration for the Error Handler, you can find the examples here.
<errorHandler id="loggingErrorHandler" type="LoggingErrorHandler" logName="foo" level="INFO" xmlns="http://camel.apache.org/schema/spring"/><!-- If don't specify type attribute, the type value will be set to DefaultErrorHandler --><errorHandler id="errorHandler" xmlns="http://camel.apache.org/schema/spring"/><!-- You can define the redeliveryPolicy inside of the errorHandler --><camel:errorHandler id="defaultErrorHandler" type="DefaultErrorHandler"> <camel:redeliveryPolicy maximumRedeliveries="2" redeliveryDelay="0" logStackTrace="false"/></camel:errorHandler><camel:errorHandler id="deadLetterErrorHandler" type="DeadLetterChannel" deadLetterUri="log:dead"> <camel:redeliveryPolicy maximumRedeliveries="2" redeliveryDelay="1000" logHandled="true" asyncDelayedRedelivery="true"/></camel:errorHandler><bean id="myErrorProcessor" class="org.apache.camel.spring.handler.MyErrorProcessor"/><!-- TX error handler can be configured using a template --><camel:errorHandler id="transactionErrorHandler" type="TransactionErrorHandler" transactionTemplateRef="PROPAGATION_REQUIRED" onRedeliveryRef="myErrorProcessor"/><!-- or using a transaction manager --><camel:errorHandler id="txEH" type="TransactionErrorHandler" transactionManagerRef="txManager"/><!-- You can also define the errorHandler inside the camelContext --><camelContext errorHandlerRef="noErrorHandler" xmlns="http://camel.apache.org/schema/spring"> <errorHandler id="noErrorHandler" type="NoErrorHandler"/></camelContext>
Using the transactional error handler
The transactional error handler is based on spring transaction. This requires the usage of the camel-spring component.
See Transactional Client that has many samples for how to use and transactional behavior and configuration with this error handler.
See also
- Error handling in Camel for introduction and background material on error handling in Camel
- Dead Letter Channel for the dead letter error handler
- DefaultErrorHandler for the default error handler in Camel
- TransactionErrorHandler for the default error handler for transacted routes
- Transactional Client for transactional behavior
- Exception Clause as it supportshandling thrown exceptions
- Try Catch Finally for try ... catch ... finally as DSL you can use in the routing
- Error Handler
- About Error Handler
- OpenCV GUI Error Handler
- mysql error handler 例
- OpenCV GUI Error Handler
- Handler中的Error
- laravel - Error in exception handler
- Error Handler/Exception Clause/Try ... Catch ... Finally
- SSIS error&failure event-handler propagate属性
- Error libc++abi.dylib handler threw exception
- PHP 错误自定义 set error handler函数
- ACPI Error:NO handler for Region [EC__]
- php - 如何恢复PHP的error handler为built in的error handler呢
- VMProcessPageFault Error: Page fault occurred while in power handler
- 解决mysql "GOT error 127 from table handler" 错误
- ERROR: Power Handler function yield to low priority thread 解决办法
- ERROR: Power Handler function yield to low priority thread. 解决方法
- OpenCV GUI Error Handler(可能文件路径不对)
- .NET设计模式:简单工厂模式
- Oracle连接视图DML操作的限制
- Linux 中 RPM 命令参数使用详解
- CSS:The Definitive Guide(3nd)
- 人生致命的八个经典问题
- Error Handler
- 一个不明白的问题
- a href onclick用法
- spring与mybatis整合之事务管理
- 电力线传输的研究(电力猫、智能家居)
- crontab命令
- 关于UIView的autoresizingMask属性的研究
- Oracle WebADI Notes
- 习惯是一件可怕的事,让人戒不掉,忘不掉。