[
https://issues.apache.org/jira/browse/AMQ-9548?focusedWorklogId=951336&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-951336
]
ASF GitHub Bot logged work on AMQ-9548:
---------------------------------------
Author: ASF GitHub Bot
Created on: 08/Jan/25 12:12
Start Date: 08/Jan/25 12:12
Worklog Time Spent: 10m
Work Description: cshannon commented on PR #1288:
URL: https://github.com/apache/activemq/pull/1288#issuecomment-2577524572
> Hey @jbonofre do you think we should put this in 6.1.5?
No, we should not be adding changes like this to a bug fix release. Releases
like 6.1.5 or 6.1.6 should just be bug fixes, security fixes, minor dependency
updates, etc.
There was a discussion started on SEMVER on the dev list that we probably
need to get back to so that it's more clear what we change in different
versions.
If new features are being developed quickly and we end up with lots of stuff
to release we can always quickly do releases. There doesn't have to be a long
wait in between 6.2.0 and 6.3.0 for example if there's a new JMS 2.0 feature
that is ready. Artemis already does this, if you look at past Artemis
[releases](https://activemq.apache.org/components/artemis/download/past_releases),
they release relatively frequently.
Issue Time Tracking
-------------------
Worklog Id: (was: 951336)
Time Spent: 10h (was: 9h 50m)
> 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: 10h
> 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
