[ 
https://issues.apache.org/jira/browse/AMQ-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732058#comment-13732058
 ] 

Dejan Bosanac commented on AMQ-4656:
------------------------------------

The first stab at fixing this is in svn revision 1511333. I changed the way 
keepDurableSubsActive works, by not stopping/starting the cursor when 
subscription (de)activates. This is a natural way in how this feature should 
work and also simplifies things a bit.



I verified the fix by running all tests with that has durable in the name, but 
we should wait for the full nightly build to see if something is broker.
                
> Pending Queue Counter is incorrect when using durable topics
> ------------------------------------------------------------
>
>                 Key: AMQ-4656
>                 URL: https://issues.apache.org/jira/browse/AMQ-4656
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.8.0
>            Reporter: Timothy Bish
>            Assignee: Dejan Bosanac
>             Fix For: 5.9.0
>
>         Attachments: AMQ4656Test.java
>
>
> When using a durable topics the Pending Queue Counter provides an incorrect 
> value for pending messages.
> Steps to recreate
> Set up the durable subscriber
> {noformat}
> ant consumer -Durl=tcp://localhost:61616 -Dtopic=true -Dsubject=MYSUB 
> -Ddurable=true -Dmax=2
> {noformat}
> Stop the subscriber
> Send 20 persistent messages
> {noformat}
> ant producer -Ddurable=true -Durl=tcp://localhost:61616 -Dtopic=true 
> -Dsubject=MYSUB -Dmax=20
> {noformat}
> Consume 2 messages
> {noformat}
> ant consumer -Durl=tcp://localhost:61616 -Dtopic=true -Dsubject=MYSUB 
> -Ddurable=true -Dmax=2
> {noformat}
> View the counter stats.
> The result is the following:
> {noformat}
> Pending Queue Size = 38
> Dispatched Queue Size = 0
> Dispatched Counter = 20
> Enqueue Counter = 20
> Dequeue Counter = 2
> {noformat}

--
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

Reply via email to