[
https://issues.apache.org/jira/browse/APLO-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399161#comment-13399161
]
Lionel Cons commented on APLO-211:
----------------------------------
I've attached a Perl script that shows the problem. When I run it against a
fresh broker (data wiped out before starting), I get:
$ perl APLO-211.pl
Subscribed, console => id=APLO-211, enqueue_item_counter=0,
dequeue_item_counter=0
Sent message & disconnected, console => id=APLO-211, enqueue_item_counter=1,
dequeue_item_counter=1
Received message & disconnected, console => id=APLO-211,
enqueue_item_counter=1, dequeue_item_counter=2
We have only one message sent and received but a dequeue counter of 2.
> 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
> Attachments: APLO-211.pl
>
>
> 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
