[jira] Updated: (AMQ-1038) Incorrect redelivery behavior and counters

["Rob Davies (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/AMQ-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Davies updated AMQ-1038:
----------------------------

         Priority: Critical  (was: Major)
    Fix Version/s:     (was: 5.2.0)
                   5.0.0

> Incorrect redelivery behavior and counters
> ------------------------------------------
>
>                 Key: AMQ-1038
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1038
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>         Environment: Windows XP Pro
> java version "1.5.0_06"
>            Reporter: Steve Bate
>            Assignee: Rob Davies
>            Priority: Critical
>             Fix For: 5.0.0
>
>         Attachments: RedeliveryTest.java
>
>
> Our understanding is that the RedeliveryPolicy maxRedeliveryCount controls the maximum number of times a message will be redelivered (assumed to be a global count and not a per-consumer count). The behavior we are seeing is that messages are redelivered more times than we specified. The problem may be related to the way the redelivery counter is being maintained. We see the redelivery counter incrementing by one for redeliveries to a specific consumer, but then it resets to a lower number when the message is redelivered to a different consumer.
> I have attached a test case to demonstrate the problem. The first test is a simple baseline example that passes. The second test shows that messages are being redelivered too many times for the redelivery policy. The third tests catches a regression in the delivery count (redelivery count + 1) when sending a rolled back message to a new consumer.
> The test suite uses an embedded broker using the VM protocol so it should be standalone.

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