[
https://issues.apache.org/jira/browse/CAMEL-4978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13200706#comment-13200706
]
Andrey Kazantsev commented on CAMEL-4978:
-----------------------------------------
Ok, maybe I don't have clear understanding of what Camel can. Could you please
explain in greater detail how can I accomplish following scenario:
1) Exception occurs in route
2) Some actions should be performed right after this, to inform external
systems (through either forwarding copy of message to another route either to
some Processor)
3) Try to redeliver this message several times
4) After redeliveries are exhausted, take another set of actions
My problem is that with DLC any logic which is written in onException is
executed only when redeliveries are exhausted and message is moved to DLQ,
while I need a way to execute some logic just after error, and after that try
to redeliver.
I will appreciate very much if you can point me a way of accomplishing this
with current means Camel already provides!
> 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
