[
https://issues.apache.org/jira/browse/AMQ-5831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712904#comment-14712904
]
ASF subversion and git services commented on AMQ-5831:
------------------------------------------------------
Commit ee54f09303f52d2753ce9ac8e64008e3e60c2eab in activemq's branch
refs/heads/master from [~dejanb]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=ee54f09 ]
https://issues.apache.org/jira/browse/AMQ-5831 - revisit topic subscriptions
> Revisit topic statistics
> ------------------------
>
> Key: AMQ-5831
> URL: https://issues.apache.org/jira/browse/AMQ-5831
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.11.0
> Reporter: Dejan Bosanac
>
> Currently, topic statistics can be confusing especially if you're using
> wildcard subscribers. In that case, inflight count and dequeue count is never
> updated when message is acked, so users can think that messages are not
> consumed.
> Statistics are primarily developed for queues and then adapted for topics,
> which is why is some of them doesn't make sense in this use case.
> To me, it'd make sense to keep only enqueue/dequeue properties on the topic,
> so that we can see general behaviour of the topic.
> Then every consumer, should keep it's own enqueue, dequeue, inflight
> (enqueue-dequeue) counts.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
