[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264335#comment-17264335 ] François Courtault commented on AMQ-7246: - Thanks a lot to answer to my request :) > 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 > Fix For: 5.17.0, 5.16.1, 5.15.15 > > Time Spent: 20m > Remaining Estimate: 0h > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264318#comment-17264318 ] ASF subversion and git services commented on AMQ-7246: -- Commit ffc09305243da186cd6535afebadba4df33bbdf4 in activemq's branch refs/heads/activemq-5.15.x from jbonofre [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=ffc0930 ] [AMQ-7246] Add scheduledMessageCount attribute on the JobSchedulerView MBean (cherry picked from commit f01e35f7d95bee8c22c5eb45b8b25375fc6ece59) > 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 > Fix For: 5.17.0, 5.16.1, 5.15.15 > > Time Spent: 20m > Remaining Estimate: 0h > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264317#comment-17264317 ] ASF subversion and git services commented on AMQ-7246: -- Commit 34bc37d68d01f71ab546cb8082ede709605a198e in activemq's branch refs/heads/activemq-5.16.x from jbonofre [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=34bc37d ] [AMQ-7246] Add scheduledMessageCount attribute on the JobSchedulerView MBean (cherry picked from commit f01e35f7d95bee8c22c5eb45b8b25375fc6ece59) > 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 > Fix For: 5.17.0, 5.16.1, 5.15.15 > > Time Spent: 20m > Remaining Estimate: 0h > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264314#comment-17264314 ] ASF subversion and git services commented on AMQ-7246: -- Commit d9febc097745b966004780ea87da84cc327c4f06 in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=d9febc0 ] Merge pull request #609 from jbonofre/AMQ-7246 [AMQ-7246] Add scheduledMessageCount and delayedMessageCount attributes on the JobSchedulerViewMBean > 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 > Fix For: 5.17.0, 5.16.1, 5.15.15 > > Time Spent: 20m > Remaining Estimate: 0h > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264313#comment-17264313 ] ASF subversion and git services commented on AMQ-7246: -- Commit f01e35f7d95bee8c22c5eb45b8b25375fc6ece59 in activemq's branch refs/heads/master from jbonofre [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=f01e35f ] [AMQ-7246] Add scheduledMessageCount attribute on the JobSchedulerView MBean > 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 > Fix For: 5.17.0, 5.16.1, 5.15.15 > > Time Spent: 20m > Remaining Estimate: 0h > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264315#comment-17264315 ] ASF subversion and git services commented on AMQ-7246: -- Commit d9febc097745b966004780ea87da84cc327c4f06 in activemq's branch refs/heads/master from Jean-Baptiste Onofré [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=d9febc0 ] Merge pull request #609 from jbonofre/AMQ-7246 [AMQ-7246] Add scheduledMessageCount and delayedMessageCount attributes on the JobSchedulerViewMBean > 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 > Fix For: 5.17.0, 5.16.1, 5.15.15 > > Time Spent: 20m > Remaining Estimate: 0h > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264114#comment-17264114 ] Jean-Baptiste Onofré commented on AMQ-7246: --- I did the PR adding two new counters (scheduledMessagesCount and delayedMessagesCount). I will do a new "manual" test before merging. It will be included in 5.16.2, 5.17.0 and 5.15.15. > 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 > Fix For: 5.17.0, 5.16.1, 5.15.15 > > Time Spent: 10m > Remaining Estimate: 0h > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263573#comment-17263573 ] François Courtault commented on AMQ-7246: - Hello Baptiste, Thanks a lot to take care about my request. If I have a solution to my issue that could be also useful for others, it's faine and don't worry. 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 > Fix For: 5.17.0, 5.16.1, 5.15.15 > > Time Spent: 10m > Remaining Estimate: 0h > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263572#comment-17263572 ] Jean-Baptiste Onofré commented on AMQ-7246: --- [~fcourtau] [https://github.com/apache/activemq/pull/609] > 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 > Fix For: 5.17.0, 5.16.1, 5.15.15 > > Time Spent: 10m > Remaining Estimate: 0h > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263495#comment-17263495 ] Jean-Baptiste Onofré commented on AMQ-7246: --- [~fcourtau] sorry about my poor handling about this Jira. My apologizes. I'm doing now the change and include for next releases. I understand you are upset (and I take the fault), but don't be too sharp. I will submit the PR soon for your review. > 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 > Fix For: 5.17.0, 5.16.1, 5.15.15 > > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263483#comment-17263483 ] Jean-Baptiste Onofré commented on AMQ-7246: --- OK, I propose to improve the JobScheduler MBean with delayed count attribute. > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[
https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263477#comment-17263477
]
François Courtault commented on AMQ-7246:
-
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, *{color:#57d9a3}I would prefer to have a dedicated
JMX counter{color}* {color:#57d9a3}{color:#172b4d}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{color}{color}{color:#57d9a3} +{color:#172b4d}isn't really the right
answer for me.{color}+{color}
{color:#57d9a3}{color:#172b4d}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}{color}
I am quite disapointed after more than one year to provide 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*
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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263342#comment-17263342 ] Jean-Baptiste Onofré commented on AMQ-7246: --- Number of jobs is delayed messages (and eventually scheduled redelivery if you have some). I'm not sure yet for JMS 2.0, but yes, I think I will use the same approach (with scheduler) for 5.18.x. > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263331#comment-17263331 ] François Courtault commented on AMQ-7246: - Baptiste, The number of Jobs = number of delayed message, right ? Should be the same with the 4.18.x with the JMS 2.0 API: setDeliveryDelay method available on Producer ? Will 4.18.x move to jakarta namespace ? 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263261#comment-17263261 ] Jean-Baptiste Onofré commented on AMQ-7246: --- 5.18.x is for second part of this year (I'm on 5.17.x for now). Yes, on the org.apache.activemq:type=Broker,brokerName=localhost,service=JobScheduler,name=JMS MBean where you have AllJobs attribute to get all jobs in the scheduler as tabular data. > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263217#comment-17263217 ] François Courtault commented on AMQ-7246: - Hello Jean-Baptiste, Thanks for the feedback. When the 4.18.x should be released ? This year ? I think we are using msg.setLongProperty(ScheduledMessage.AMQ_SCHEDULED_DELAY, delay). Is there any JMX counter for message in the scheduler ? If no, how to get this information ? Any performance impact by not using JMX ? 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[
https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263208#comment-17263208
]
Jean-Baptiste Onofré commented on AMQ-7246:
---
ActiveMQ 5.5.x is JMS 1.1 for now (JMS 2.0 will come in 5.18.x).
The delivery delay is the minimum time once the message has been produced
before the message is available to "consumption".
Inflight count is the number of messages sent to a consumer session and have
not received an ack.
Dispatch count is the total number of messages sent to consumer sessions
(Dequeue + Inflight).
So, inflight + dispatch is not related to production, but just consumption.
In your case, with ActiveMQ 5.x (JMS 1.1 for now), you can use:
{code:java}
msg.setLongProperty(ScheduledMessage.AMQ_SCHEDULED_DELAY, delay); {code}
You will have a delayed message (the scheduler should be enabled).
Then, you can check all message in the scheduler.
> 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263204#comment-17263204 ] François Courtault commented on AMQ-7246: - Hello, When I said delayed message, I was refering to JMS 2.0 setDeliveryDelay method available on Producer. I know that ActiveMQ is not JMS 2.0 compliant. I don't think I have understood your answer. My current understanding is: delayed messages = inflight + dispatch ? Could you provide me please the formula to apply in order to have the number of messages delayed ? BTW will, at some point, ActiveMQ be JMS 2.0 certified ? 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17263102#comment-17263102 ] Jean-Baptiste Onofré commented on AMQ-7246: --- Hi, You already have: * queue size for the number of pending message * inflight and dispatch for the "delayed" (even if it's not "direct", assuming that you mean delayed == redelivered, you can also check the redeliveryCount). > 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 > Fix For: 5.17.0, 5.16.1, 5.15.15 > > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231968#comment-17231968 ] Jean-Baptiste Onofré commented on AMQ-7246: --- For Artemis, it's up to you (I'm working on ActiveMQ). Regarding ActiveMQ, yes, it will be included in next releases cycle. > 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 > Fix For: 5.17.0, 5.16.1, 5.15.14 > > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231965#comment-17231965 ] François Courtault commented on AMQ-7246: - Hello again, I also looked at the Artemis documentation at [https://activemq.apache.org/components/artemis/documentation/latest/management.html] and the counters available (section Message Counters) are: * count * countDelta * messageCount * messageCountDelta * lastAddTimestamp * lastAckTimestamp * updateTimestamp Si it seems that the delayed message is not included in these counters as well. Should I add an enhancement request on Artemis ? 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 > Fix For: 5.16.1, 5.15.14 > > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231963#comment-17231963 ] François Courtault commented on AMQ-7246: - Hello again, A question: how to know, at instant t, how many messages are in the queue ? using JMX QueueSize ? using JMX InFlightCount ? using the formula EnqueueCount - DequeueCount ? Just also to be sure: the delayed message count is not included in any of these counters above until the delay time has expired, right ? 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 > Fix For: 5.16.1, 5.15.14 > > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231961#comment-17231961 ] François Courtault commented on AMQ-7246: - Hello, Any update on this request ? Will it be implemented finally and when ? 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 > Fix For: 5.16.1, 5.15.14 > > > 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)
[jira] [Commented] (AMQ-7246) Having a JMX counter for delayed messages
[ https://issues.apache.org/jira/browse/AMQ-7246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043200#comment-17043200 ] François Courtault commented on AMQ-7246: - Hello, The 26/Jul/19, the Fix Versions was set to 5.15.11 and 5.16.0 So it means that it's delayed, right ? The question I have then is: when 5.15.13 and 5.16.1 ((including this fix) will be delivered ? 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 > Fix For: 5.15.13, 5.16.1 > > > 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)
