activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-1038) Incorrect redelivery behavior and counters
Date Wed, 03 Oct 2007 23:36:23 GMT

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

Hiram Chirino resolved AMQ-1038.
--------------------------------

    Resolution: Fixed
      Assignee: Hiram Chirino  (was: Rob Davies)

We have now fixed this in rev 581747.  

The test case need to be sightly adjusted because every time rollback() occurs the redelivery
counter is increased and when the consumer  holding the dispatched message is closed, the
redelivery counter is also increased.  So by the time the fist consumer in the test case closes
out it's session, the message will be marked redelivered as 4 times (test case assumes it
will only be redelivered 3 times, 1 for each rollback).

> 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: Hiram Chirino
>            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.


Mime
View raw message