[
https://issues.apache.org/jira/browse/AMQ-9775?focusedWorklogId=984527&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-984527
]
ASF GitHub Bot logged work on AMQ-9775:
---------------------------------------
Author: ASF GitHub Bot
Created on: 25/Sep/25 13:12
Start Date: 25/Sep/25 13:12
Worklog Time Spent: 10m
Work Description: jbonofre opened a new pull request, #1500:
URL: https://github.com/apache/activemq/pull/1500
This PR adds the `maxBrowsePageSize` attribute to the JMX destination MBean.
As described in the Jira (AMQ-9775), the `maxBrowsePageSize` property can be
set in the destination policies, in the broker.
I have several use cases where client applications are interested to get
this metric (via JMX or REST with Jolokia):
* know the browse paging limit to "optimize" paging/browsing on client side
(faster)
* get detail about the limit to "recommend" update on the paging limit
Issue Time Tracking
-------------------
Worklog Id: (was: 984527)
Remaining Estimate: 0h
Time Spent: 10m
> Add maxBrowsePageSize attribute on the JMX destination MBean
> ------------------------------------------------------------
>
> Key: AMQ-9775
> URL: https://issues.apache.org/jira/browse/AMQ-9775
> Project: ActiveMQ Classic
> Issue Type: Improvement
> Components: JMX
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 6.2.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> {{maxBrowsePageSize}} is a configuration users can define via destination
> policy. Implicitly it can "impact" the clients and their browsing "limit".
> However, there's no way (at runtime) to see this configuration.
> {{maxBrowsePageSize}} should be included in the JMX destination MBean.
--
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
