You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Lionel Cons (JIRA)" <ji...@apache.org> on 2012/06/05 13:59:24 UTC
[jira] [Created] (APLO-211) Incorrect dequeued counter for topics
Lionel Cons created APLO-211:
--------------------------------
Summary: 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
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
[jira] [Commented] (APLO-211) Incorrect dequeued counter for topics
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398597#comment-13398597 ]
Hiram Chirino commented on APLO-211:
------------------------------------
Got the config / test procedure?
> 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
[jira] [Assigned] (APLO-211) Incorrect dequeued counter for topics
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino reassigned APLO-211:
----------------------------------
Assignee: Hiram Chirino
> 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
[jira] [Commented] (APLO-211) Incorrect dequeued counter for topics
Posted by "Lionel Cons (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (APLO-211) Incorrect dequeued counter for topics
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated APLO-211:
-------------------------------
Component/s: apollo-broker
Fix Version/s: 1.4
> Incorrect dequeued counter for topics
> -------------------------------------
>
> Key: APLO-211
> URL: https://issues.apache.org/jira/browse/APLO-211
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker
> Environment: apollo-99-trunk-20120519.032132-42
> Reporter: Lionel Cons
> Assignee: Hiram Chirino
> Fix For: 1.4
>
> 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
[jira] [Commented] (APLO-211) Incorrect dequeued counter for topics
Posted by "Lionel Cons (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13292679#comment-13292679 ]
Lionel Cons commented on APLO-211:
----------------------------------
I've tried with the latest snapshot and I still see the problem.
Here is the config I use wrt destinations:
<queue auto_delete_after="604800"/>
<topic auto_delete_after="604800" slow_consumer_policy="queue"/>
<dsub auto_delete_after="604800"/>
If this is not enough to reproduce the problem, I'll send you the complete config separately.
> 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
[jira] [Commented] (APLO-211) Incorrect dequeued counter for topics
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Resolved] (APLO-211) Incorrect dequeued counter for topics
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino resolved APLO-211.
--------------------------------
Resolution: Fixed
Fixed. Will show up in the next snapshot build.
> Incorrect dequeued counter for topics
> -------------------------------------
>
> Key: APLO-211
> URL: https://issues.apache.org/jira/browse/APLO-211
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker
> Environment: apollo-99-trunk-20120519.032132-42
> Reporter: Lionel Cons
> Assignee: Hiram Chirino
> Fix For: 1.4
>
> 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
[jira] [Updated] (APLO-211) Incorrect dequeued counter for topics
Posted by "Lionel Cons (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lionel Cons updated APLO-211:
-----------------------------
Attachment: APLO-211.pl
> 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
[jira] [Commented] (APLO-211) Incorrect dequeued counter for topics
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13291774#comment-13291774 ]
Hiram Chirino commented on APLO-211:
------------------------------------
Is your topic using the default configuration?
> 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