camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Commented: (CAMEL-960) DeadLetterChannel - option to mark the exchange as failure handled and that its OK
Date Fri, 10 Oct 2008 05:03:52 GMT


Claus Ibsen commented on CAMEL-960:


if (processor != null) {
  data.failureProcessor = processor;

A good idea, however the default processor in DLC is a Logger that logs at ERROR, so the processor
is by default != null.
I don't think logging it at ERROR should be considered as handled. But yet again the default
currently in Camel with DLC and TransctedExchanges etc. is up for a revision in Camel 2.0.

With your idea then the catch-22 from above will work. Could you try the change and see how
many unit tests breaks ;)

> DeadLetterChannel - option to mark the exchange as failure handled and that its OK
> ----------------------------------------------------------------------------------
>                 Key: CAMEL-960
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Hadrian Zbarcea
>             Fix For: 1.5.0, 2.0.0
> Currently the DeadLetterChannel sets the orignal caused exception on the exchange *after*
it has been failure handled. We should support somekind of option to enable/disable this feature.
We could support:
> - option on the endpoint to set this for all exchanges
> - support a special header key that end-users can insert per exchange to be more dynamic
> - maybe methods on Exchange to set this more easily
> - maybe some refinements in isFailureHandled() to cater for this
> And we should consider use a better keyname in the DLC where it stores the original exception.

> See nabble:
> We might need to push this for Camel 2.0 but I think it is a feature that end-users would
need sooner.
> Any thoughts, please write here?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message