[
https://issues.apache.org/jira/browse/ARTEMIS-3516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17425419#comment-17425419
]
Lasse Lindgård commented on ARTEMIS-3516:
-----------------------------------------
It sounds very nice that you already have the numbers.
I am using the ClientSession.QueueQuery and in that interface I can only see
the messageCount.
Would it be possible to expose the deliveringCount in that interface as well?
And maybe a sugar method that subtracts the two numbers.
Also it would be very helpful if the information was more readily available
from the management console.
As a user the default behavior is non obvious and it looks like an error. It
took me a long time testing and reading the docs to figure out the the batching
was playing with me.
> 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)
