[
https://issues.apache.org/jira/browse/ARTEMIS-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17782343#comment-17782343
]
Justin Bertram commented on ARTEMIS-4482:
-----------------------------------------
bq. Wanted to rollout the same setting to all envs and not have users need to
select it themselves.
As far as I'm aware this isn't possible.
bq. Could you share your setup to test?
I created & started a broker:
{noformat}
./artemis create consoleTest --user=x --password=x --allow-anonymous
cd consoleTest/bin
./artemis run{noformat}
Then I ran this script to create the addresses & queues:
{noformat}
#!/bin/bash
for i in {0..300}
do
./artemis queue create --name=$i --address=$i --anycast --durable
--preserve-on-no-consumers --auto-create-address
done{noformat}
The I opened up the web console and poked around a bit. I refreshed the browser
a bunch of times. Everything remained responsive and working normally as far as
I could tell.
> 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: Bildschirmaufnahme 2023-11-02 um 08.27.58.mov,
> Bildschirmaufnahme 2023-11-02 um 08.41.34.mov, 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)
