You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Steve Bate (JIRA)" <ji...@apache.org> on 2006/11/09 21:21:02 UTC
[jira] Created: (AMQ-1038) Incorrect redelivery behavior and
counters
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
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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-1038) Incorrect redelivery behavior and
counters
Posted by "Barry Kaplan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37938 ]
Barry Kaplan commented on AMQ-1038:
-----------------------------------
Any chance that this will get some attention? The current behavior pretty much requires that redelivery be implemented in client code by incrementing a message property and putting a cloned message back on the queue.
> 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
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira