[
https://issues.apache.org/jira/browse/CAMEL-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202204#comment-13202204
]
Claus Ibsen commented on CAMEL-4978:
------------------------------------
Andrey
Sorry for not getting back sooner.
You use-case seems compelling. The draw-back is that we would need to add more
options to the error handling in Camel. And to find a good term for the new
feature, to avoid confusion.
If there is a *onError* then people may get confused/mixed up with
*onException* and what the difference would be.
And what is the difference between error/exception? Isn't it the same?
And should you be able to configure *onError* on both the *errroHandler* and
the *onException* like you can do with other options such as redelivery
options, and onRedelivery.
Is there not a better term than onError? I think it should start with onXXX
just like onRedelivery. But something that will not confuse people.
> Dead Letter Channel: add onError with correspondence to onRedelivery
> --------------------------------------------------------------------
>
> Key: CAMEL-4978
> URL: https://issues.apache.org/jira/browse/CAMEL-4978
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: Future
> Reporter: Andrey Kazantsev
> Priority: Minor
> Labels: features
>
> When an error occurs there can be situation when some actions should be
> performed before next redelivery attempt. These actions can be custom logging
> (in case of Dead Letter Channel we don't have control on logger name and
> format), creating incident request in internal company system, etc.
> Current version of Dead Letter Channel provides support for specifying
> processor which is called when next redelivery attempt is performed. However,
> if delay between attempts is long, this can be too late.
> I think we can implement support for specifying processor which will be
> called when error occurs, e.g., onError property. Then this processor with
> information from provided Exchange can take appropriate actions. For example,
> it can save this message for further investigation, while Dead Letter Channel
> will keep going on redelivering it.
> If this feature is worth to be implemented, I can prepare a patch. I
> implemented a work-around in my current project using onRedelivery, but I
> don't like it because of latency in redelivery interval.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
