You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2008/08/27 08:13:52 UTC
[jira] Commented: (CAMEL-857) DeadLetterChannel - maximum
redelivery is not corrent and redelivery counter is wrong when failure
handled
[ https://issues.apache.org/activemq/browse/CAMEL-857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45181#action_45181 ]
Claus Ibsen commented on CAMEL-857:
-----------------------------------
Also the redelivery boolean flag was always TRUE even though there was no attempt of redelivery. This is also fixed now.
> 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.