[
https://issues.apache.org/jira/browse/AMQ-7246?focusedWorklogId=535580&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-535580
]
ASF GitHub Bot logged work on AMQ-7246:
---------------------------------------
Author: ASF GitHub Bot
Created on: 13/Jan/21 17:49
Start Date: 13/Jan/21 17:49
Worklog Time Spent: 10m
Work Description: jbonofre merged pull request #609:
URL: https://github.com/apache/activemq/pull/609
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 535580)
Time Spent: 20m (was: 10m)
> 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)
