[
https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263477#comment-17263477
]
François Courtault edited comment on AMQ-7246 at 1/12/21, 4:55 PM:
-------------------------------------------------------------------
Hello Jean-Baptiste,
Your proposal is similar to what I have written since the begining :(
"One possibility is to use the getAllJobs() operation on JobScheduler MBean.
{color:#de350b}*But we have to specify a timeframe so it's quite difficult to
use.*{color}"
So, as it's not so handy. I would prefer *{color:#57d9a3}to have a dedicated
JMX counter{color}* and at some point *you make me believe that you will
deliver a fix for that*. *A fix you postponed several times.* So the
resolution which is set to NOT A PROBLEM +isn't really the right answer for
me.+
At a given moment, ActiveMQ is not able to provide me the number of messages
delayed (eg the number of messages not being available for consumption) !!!
*{color:#de350b}I am quite disapointed.{color}* After +more than one year+ that
ActiveMQ provides me a solution which is not what I expect and that I have also
described since the begining :(
Artemis is providing such info
[http://activemq.apache.org/components/artemis/documentation/latest/metrics.html]
: *scheduled.message.count*
Why not ActiveMQ?
Best Regards.
was (Author: fcourtau):
Hello Jean-Baptiste,
Your proposal is similar to what I have written since the begining :(
"One possibility is to use the getAllJobs() operation on JobScheduler MBean.
{color:#de350b}*But we have to specify a timeframe so it's quite difficult to
use.*{color}"
So, as it's not so handy. I would prefer *{color:#57d9a3}to have a dedicated
JMX counter{color}* and at some point *you make me believe that you will
deliver a fix for that*. *A fix you postponed several times.* So the
resolution which is set to NOT A PROBLEM +isn't really the right answer for
me.+
At a given moment, ActiveMQ is not able to provide me the number of messages
delayed (eg the number of messages not being available for consumption) !!!
I am quite disapointed. After more than one year that ActiveMQ provides me a
solution which is not what I expect and that I have also described since the
begining :(
Artemis is providing such info
[http://activemq.apache.org/components/artemis/documentation/latest/metrics.html]
: *scheduled.message.count*
Why not ActiveMQ?
Best Regards.
> Having a JMX counter for delayed messages
> -----------------------------------------
>
> Key: AMQ-7246
> URL: https://issues.apache.org/jira/browse/AMQ-7246
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JMX
> Affects Versions: 5.15.6
> Reporter: François Courtault
> Assignee: Jean-Baptiste Onofré
> Priority: Major
>
> As of today there is no easy way to monitor the number of delayed messages.
> One possibility is to use the getAllJobs() operation on JobScheduler MBean.
> But we have to specify a timeframe so it's quite difficult to use.
> Instead, could we have a new JMX counter which provides the number of delayed
> messages ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
