You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Alberto Aresca (JIRA)" <ji...@apache.org> on 2013/06/25 21:25:19 UTC

[jira] [Updated] (AMQ-4601) Redelivery counter does not behave properly when closing consumer

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

Alberto Aresca updated AMQ-4601:
--------------------------------

    Attachment: activemq-redelivery-issue.zip
    
> Redelivery counter does not behave properly when closing consumer
> -----------------------------------------------------------------
>
>                 Key: AMQ-4601
>                 URL: https://issues.apache.org/jira/browse/AMQ-4601
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client
>    Affects Versions: 5.8.0
>            Reporter: Alberto Aresca
>         Attachments: activemq-redelivery-issue.zip
>
>
> Attached a test case that does the following: 
> 1. Registers 4 consumers. 
> 2. Sends a message. 
> 3. When the first message is received, it does the following:
> 3.1. Unregister the listeners for the consumers. 
> 3.2. Close the consumers. 
> 3.3. Rollback the transaction. 
> 4. Consume the message from a new consumer
> After running the test called TestActiveMqRedeliveryIssue you will see in the logs (among others things): 
> delivery count 1 
> delivery count 5 
> The first one corresponds to the first message and the second one to the message that is consumed from the queue after the stop() procedure was called. 
> As you can see, the count increased by 4, which is the number of consumers. 
> The expected behaviour would be to have the redelivery counter set to 1 when the message is consumed the second time

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira