You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2012/08/13 18:30:38 UTC
[jira] [Created] (APLO-240) Aggregate destination metrics invalid
when using topic slow_consumer_policy="queue"
Hiram Chirino created APLO-240:
----------------------------------
Summary: Aggregate destination metrics invalid when using topic slow_consumer_policy="queue"
Key: APLO-240
URL: https://issues.apache.org/jira/browse/APLO-240
Project: ActiveMQ Apollo
Issue Type: Bug
Components: apollo-broker, apollo-web
Affects Versions: 1.4
Reporter: Hiram Chirino
Assignee: Hiram Chirino
Fix For: 1.5
Originally identified on APOLO-239.
Scenario: accessing /dest-metrics with topics configured with slow_consumer_policy="queue" and
using a single topic and two consumers, one message received by the broker (and therefore two messages sent by the broker to the two consumers) will result in enqueue_item_counter+=3 and dequeue_item+=4 instead of the expected +1 and +2.
--
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-240) Aggregate destination metrics invalid
when using topic slow_consumer_policy="queue"
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433320#comment-13433320 ]
Hiram Chirino commented on APLO-240:
------------------------------------
Fix is being deployed in build:
https://builds.apache.org/job/ActiveMQ-Apollo-Deploy/276/
> Aggregate destination metrics invalid when using topic slow_consumer_policy="queue"
> -----------------------------------------------------------------------------------
>
> Key: APLO-240
> URL: https://issues.apache.org/jira/browse/APLO-240
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker, apollo-web
> Affects Versions: 1.4
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 1.5
>
>
> Originally identified on APOLO-239.
> Scenario: accessing /dest-metrics with topics configured with slow_consumer_policy="queue" and
> using a single topic and two consumers, one message received by the broker (and therefore two messages sent by the broker to the two consumers) will result in enqueue_item_counter+=3 and dequeue_item+=4 instead of the expected +1 and +2.
--
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-240) Aggregate destination metrics invalid
when using topic slow_consumer_policy="queue"
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino resolved APLO-240.
--------------------------------
Resolution: Fixed
> Aggregate destination metrics invalid when using topic slow_consumer_policy="queue"
> -----------------------------------------------------------------------------------
>
> Key: APLO-240
> URL: https://issues.apache.org/jira/browse/APLO-240
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Components: apollo-broker, apollo-web
> Affects Versions: 1.4
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 1.5
>
>
> Originally identified on APOLO-239.
> Scenario: accessing /dest-metrics with topics configured with slow_consumer_policy="queue" and
> using a single topic and two consumers, one message received by the broker (and therefore two messages sent by the broker to the two consumers) will result in enqueue_item_counter+=3 and dequeue_item+=4 instead of the expected +1 and +2.
--
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