[
https://issues.apache.org/jira/browse/AMQ-9775?focusedWorklogId=1004600&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1004600
]
ASF GitHub Bot logged work on AMQ-9775:
---------------------------------------
Author: ASF GitHub Bot
Created on: 11/Feb/26 13:51
Start Date: 11/Feb/26 13:51
Worklog Time Spent: 10m
Work Description: jeanouii commented on PR #1500:
URL: https://github.com/apache/activemq/pull/1500#issuecomment-3884570296
The ticket refers to being able to provide a configuration option
(maxBrowsePageSize), but the PR also includes the ability to update it. If this
is intended, then we probably need to update the ticket and check the impact of
updating the property at runtime. If it's not intended, we can I think remove
the setter and not necessarly have tons of tests, it's read-only.
Issue Time Tracking
-------------------
Worklog Id: (was: 1004600)
Time Spent: 40m (was: 0.5h)
> Add maxBrowsePageSize attribute on the JMX destination MBean
> ------------------------------------------------------------
>
> Key: AMQ-9775
> URL: https://issues.apache.org/jira/browse/AMQ-9775
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JMX
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 6.3.0
>
> Time Spent: 40m
> 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
