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 2021/10/05 18:04:00 UTC

[jira] [Commented] (ARTEMIS-3516) Smarter message count

    [ https://issues.apache.org/jira/browse/ARTEMIS-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17424633#comment-17424633 ] 

Justin Bertram commented on ARTEMIS-3516:
-----------------------------------------

This already exists in essence. The {{deliveringCount}} denotes the number dispatched-but-not-acknowledged messages (i.e. messages that are "in delivery"). You can subtract the {{deliveringCount}} from the {{messageCount}} to determine the number of "undelivered" messages.

> Smarter message count
> ---------------------
>
>                 Key: ARTEMIS-3516
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-3516
>             Project: ActiveMQ Artemis
>          Issue Type: Wish
>          Components: Broker
>    Affects Versions: 2.17.0
>            Reporter: Lasse LindgÄrd
>            Priority: Major
>
> I am not going to tell you how, but one wish could be that it could be configured timebased, so that acks are sent at least every minute. Or the consumer could be smart about how busy it is and send acks on every message when the message rate is below some number.
> Another way to think of this is in terms of user experience. I now understand that the message count includes inflight messages. But I would really like to have one number for inflight and one number for undelivered messages.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)