activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMQ-5831) Revisit topic statistics
Date Wed, 26 Aug 2015 10:33:46 GMT

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

Dejan Bosanac resolved AMQ-5831.
--------------------------------
       Resolution: Fixed
         Assignee: Dejan Bosanac
    Fix Version/s: 5.13.0

Fixed. After the work on [AMQ-5837], we now track dispatched messages which made it easier
to implement statistic semantics similar to queues. I also changed semantics of durable subscribers
to increment dequeue count on each ack.

> 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
>            Assignee: Dejan Bosanac
>             Fix For: 5.13.0
>
>
> 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)

Mime
View raw message