You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Justin Bertram (JIRA)" <ji...@apache.org> on 2018/10/12 18:00:00 UTC

[jira] [Closed] (ARTEMIS-1855) Add a JMX attribute for the number of messages received by an address

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

Justin Bertram closed ARTEMIS-1855.
-----------------------------------
    Resolution: Duplicate

> Add a JMX attribute for the number of messages received by an address
> ---------------------------------------------------------------------
>
>                 Key: ARTEMIS-1855
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1855
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: Lionel Cons
>            Priority: Major
>
> On a broker with {{multicastPrefix}} set to emulate the standard STOMP destinations, I am sending messages (using a STOMP producer) to {{/topic/test}} when there are no consumers.
> The "number of messages" attributes (both {{MessageCount}} and {{NumberOfMessages}}) stay at 0. FWIW, they get incremented when using a queue instead of a topic.
> This is not really a bug since these attributes are documented as
> * {{MessageCount}}: number of messages added to all the queues for this address
> * {{NumberOfMessages}}: the sum of messages on queue(s), including messages in delivery
> For monitoring purposes, I want to track the number of messages received by a topic, even with no consumers (so no queues) attached. The goal is to get the incoming message rate.
> Could one or more JMX attributes be added to keep track of all received messages?
> Note that this is tricky because, with the current implementation, both {{/topic/test}} and {{/queue/test}} use the same {{test}} address. Since these two destinations are different (see also ARTEMIS-1794), they should get different counters for incoming messages.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)