[
https://issues.apache.org/jira/browse/ARTEMIS-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781769#comment-17781769
]
Justin Bertram commented on ARTEMIS-4482:
-----------------------------------------
This is likely due to the automatic refresh functionality used by the console
by default. If there are lots of addresses and queues then the amount of
information fetched from the broker and processed by the console can be quite
large which can cause unresponsiveness. You can change this behavior by
selecting the "Preferences" in the top right and then clicking the "Jolokia"
tab. You can either disable the "Update rate" or choose a longer period. See
here:
!jolokia-prefs.png!
You can also tune how much data is fetched using the "Max depth" and "Max
collection size" options.
> Management console becomes unresponsive with ~300 queues/addresses
> ------------------------------------------------------------------
>
> Key: ARTEMIS-4482
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4482
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: JMX
> Affects Versions: 2.29.0, 2.31.2
> Reporter: Moritz Schmitz von Hülst
> Priority: Major
> Attachments: Screenshot 2023-11-01 at 09-25-59 Artemis Console.png,
> jolokia-prefs.png
>
>
> We somehow ran into the problem that the console for managing Artemis becomes
> unresponsive every now and then.
> I set up a guide on how I could reproduce this in a local k8s cluster using
> kind:
> [https://gist.github.com/moritzschmitz-oviva/eaeec3b143e050b3da23131a3b82ce73]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
