camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-857) DeadLetterChannel - maximum redelivery is not corrent and redelivery counter is wrong when failure handled
Date Wed, 27 Aug 2008 06:13:52 GMT

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

Claus Ibsen commented on CAMEL-857:
-----------------------------------

Okay is fixing this now.

Camel will now as before do by default: 1 regular attempt + 5 re-deliveries = a total of 6
times to process an exchange before moving to the dead letter channel.
Camel does this in 1.4 or older, just the counter was wrong when you was reading it from the
dead letter channel after it was moved there. 

> DeadLetterChannel - maximum redelivery is not corrent and redelivery counter is wrong
when failure handled
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-857
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-857
>             Project: Apache Camel
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 1.5.0
>
>
> The unit test from CAMEL-794 demonstrates a few issues with the DLC in Camel
> - the maximum redelivery is not reached - eg. setting it to 2 will only perform 1 normal
attempt + 1 redelivery, and not as expected 2 redeliveries
> - when the exchanged could *not* be redelivered at all then the redeliverycounter has
already been incremented and thus is off by +1

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


Mime
View raw message