AMQ-9775: Add the maxBrowsePageSize attribute to the JMX destination MBean #1500
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I can add a test about this new JMX attribute. |
|
@jbonofre please add a test for queue AND topic subscription recovery policy to catch regression |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds the
maxBrowsePageSizeattribute to the JMX destination MBean.As described in the Jira (AMQ-9775), the
maxBrowsePageSizeproperty 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):