[ 
https://issues.apache.org/jira/browse/ARTEMIS-5120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891946#comment-17891946
 ] 

Justin Bertram edited comment on ARTEMIS-5120 at 10/22/24 5:19 PM:
-------------------------------------------------------------------

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.


was (Author: jbertram):
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.

> Make Artemis console not render broker diagram initially
> --------------------------------------------------------
>
>                 Key: ARTEMIS-5120
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-5120
>             Project: ActiveMQ Artemis
>          Issue Type: Task
>          Components: Web Console
>            Reporter: Josh Byster
>            Priority: Minor
>         Attachments: StackOverflow.png, jolokia-prefs.png
>
>
> With lots of connections, consumers, etc., the Artemis console fails to load 
> because it seems to try and render it initially on landing on the console 
> page. It will cause a crash often due to a stack overflow. This should only 
> be loaded if we want to be looking at the broker diagram.



--
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


Reply via email to