[
https://issues.apache.org/jira/browse/AMQ-9548?focusedWorklogId=939804&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-939804
]
ASF GitHub Bot logged work on AMQ-9548:
---------------------------------------
Author: ASF GitHub Bot
Created on: 23/Oct/24 19:25
Start Date: 23/Oct/24 19:25
Worklog Time Spent: 10m
Work Description: cshannon commented on PR #1288:
URL: https://github.com/apache/activemq/pull/1288#issuecomment-2433258837
Also the naming doesn't matter, can pick whatever makes sense. The point is
just provide both metrics as they could both be useful but make sure we compute
them without a bunch of memory allocation
Issue Time Tracking
-------------------
Worklog Id: (was: 939804)
Time Spent: 8h 10m (was: 8h)
> Add new broker mbean attributes to directly retrieve total number of queues
> and topics
> --------------------------------------------------------------------------------------
>
> Key: AMQ-9548
> URL: https://issues.apache.org/jira/browse/AMQ-9548
> Project: ActiveMQ Classic
> Issue Type: Improvement
> Components: JMX
> Affects Versions: 5.18.5, 6.1.2
> Reporter: Ken Liao
> Assignee: Ken Liao
> Priority: Major
> Fix For: 6.2.0
>
> Time Spent: 8h 10m
> Remaining Estimate: 0h
>
> Right now, to monitor the number of destination, the only way is to read the
> destinations MBean and get the total destination. However, this means reading
> all destination names into memory, if the user has 10K+ destination with long
> destination name, it will be a large amount of memory just to monitor the
> number of them.
> The proposal here is to add either a new MBean value or a method to obtain
> that data. We can also add a method to retrieve the first K destination as
> well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
