You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/04/25 09:34:15 UTC

[jira] [Commented] (CAMEL-6311) DeadLetterChannel - When messages sent to DLQ it should always regard it as handled = true

    [ https://issues.apache.org/jira/browse/CAMEL-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13641526#comment-13641526 ] 

Claus Ibsen commented on CAMEL-6311:
------------------------------------

This problem is only if you use a custom onException that do *not* have handled=true, then that overrides the handling on the DLC which was the bug.
                
> DeadLetterChannel - When messages sent to DLQ it should always regard it as handled = true
> ------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-6311
>                 URL: https://issues.apache.org/jira/browse/CAMEL-6311
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core, camel-jms
>    Affects Versions: 2.10.4, 2.11.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.10.5, 2.11.1
>
>
> See nabble
> http://camel.465427.n5.nabble.com/DeadLetterChanel-does-not-handle-exception-tp5731073.html
> You may have a situation when using DeadLetterChannel, and it handles an exception. Then afterwards in the consumer, they should see the Exchange being regarded as handled, with no exception if they call getException.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira