You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2015/04/23 16:26:38 UTC

[jira] [Resolved] (AMQ-5742) Destination dispatched count statistic not reflecting redelivery/redispatch

     [ https://issues.apache.org/jira/browse/AMQ-5742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-5742.
-----------------------------
    Resolution: Fixed

fix in http://git-wip-us.apache.org/repos/asf/activemq/commit/c85fa67e

> Destination dispatched count statistic not reflecting redelivery/redispatch
> ---------------------------------------------------------------------------
>
>                 Key: AMQ-5742
>                 URL: https://issues.apache.org/jira/browse/AMQ-5742
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.11.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: dispatchedCount, jmx, statistics
>             Fix For: 5.12.0
>
>
> Tracking down in intermittent failure of org.apache.activemq.network.DemandForwardingBridgeTest.testSendThenAddConsumer
> the problem turned out to be a decrement of the dispatched count when the consumer was removed.
> So before the removal, most of the time, the stat was 1, and the test passed. But if the removal was complete, the dispatched count was decremented in error by the unacked message count. This is wrong. The dispatched stat needs to reflect what happened :-) Otherwise it tracks the dequeue count.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)