activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APLO-211) Incorrect dequeued counter for topics
Date Fri, 08 Jun 2012 14:18:23 GMT

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

Hiram Chirino commented on APLO-211:
------------------------------------

I just tried this out and could not reproduce.  I tried with the 'slow_consumer_policy="queue"'
option and with out.
I was using the included websocket example to drive some traffic to the topic and I saw the
counters stay correct.
                
> Incorrect dequeued counter for topics
> -------------------------------------
>
>                 Key: APLO-211
>                 URL: https://issues.apache.org/jira/browse/APLO-211
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>         Environment: apollo-99-trunk-20120519.032132-42
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>
> The dequeued counter for topics seems to go wrong when subscribers disconnect.
> Here is how to reproduce:
>  - start with a fresh topic: all counters are at 0
>  - start a consumer
>  - start a producer that sends one message and disconnect, we get: enqueued=1, dequeued=1,
dispatched=1
>  - stop the consumer, we now get: enqueued=1, dequeued=2
> FWIW, when using a queue, the dequeued counter stays at one even after the consumer disconnection.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message