[jira] [Commented] (ARTEMIS-4482) Management console becomes unresponsive with ~300 queues/addresses
[ https://issues.apache.org/jira/browse/ARTEMIS-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782653#comment-17782653 ] Justin Bertram commented on ARTEMIS-4482: - I'm not sure where to go from here. Without a way to reproduce it there's not much I can do to investigate further. > 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)
[jira] [Commented] (ARTEMIS-4482) Management console becomes unresponsive with ~300 queues/addresses
[
https://issues.apache.org/jira/browse/ARTEMIS-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782456#comment-17782456
]
Moritz Schmitz von Hülst commented on ARTEMIS-4482:
---
Also no success with the containerized versions.
{code:java}
docker run --rm --name broker -p=8161:8161
-e=JAVA_ARGS_APPEND=-Dwebconfig.bindings.artemis.uri=http://0.0.0.0:8161
-e=AMQ_USER=x -e=AMQ_PASSWORD=x
quay.io/artemiscloud/activemq-artemis-broker-kubernetes:artemis.2.31.0{code}
{code:java}
docker exec broker /opt/amq/bin/artemis queue create --name=$i --address=$i
--anycast --durable --preserve-on-no-consumers --auto-create-address{code}
> 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)
[jira] [Commented] (ARTEMIS-4482) Management console becomes unresponsive with ~300 queues/addresses
[ https://issues.apache.org/jira/browse/ARTEMIS-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782438#comment-17782438 ] Moritz Schmitz von Hülst commented on ARTEMIS-4482: --- I was not able to reproduce this with the standalone release. Will try it now with a containerized version, non-k8s. > 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)
[jira] [Commented] (ARTEMIS-4482) Management console becomes unresponsive with ~300 queues/addresses
[
https://issues.apache.org/jira/browse/ARTEMIS-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (ARTEMIS-4482) Management console becomes unresponsive with ~300 queues/addresses
[ https://issues.apache.org/jira/browse/ARTEMIS-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782335#comment-17782335 ] Moritz Schmitz von Hülst commented on ARTEMIS-4482: --- [~jbertram], I meant 'Infrastructure as Code'. Wanted to rollout the same setting to all envs and not have users need to select it themselves. Could you share your setup to test? My observation is that the console only becomes unresponsive after a couple of refreshes in the browser. And is easier to reproduce the faster you hit refresh. I will also try to setup a config with docker only tomorrow (or even standalone) to reproduce. > 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)
[jira] [Commented] (ARTEMIS-4482) Management console becomes unresponsive with ~300 queues/addresses
[ https://issues.apache.org/jira/browse/ARTEMIS-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782301#comment-17782301 ] Justin Bertram commented on ARTEMIS-4482: - bq. ...I still run into the issue that when I refresh and don't wait for the page to load yet... I'm not sure what you mean by this. Can you elaborate? bq. ...I am able to get into a state where the console doesn't load at all anymore. Even if you refresh the browser the console won't load? bq. ...Can I set these preferences somewhere in the configuration files? As IaC? Do you mean in server-side configuration files? If so, no. As far as I'm aware these settings can only be set from the web console. What is "IaC"? As a proof-of-concept I created a default instance of 2.31.0 and created 300 addresses with 1 anycast queue each and then tried to use the web console. Everything worked fine. Can you provide me instructions to reproduce what you're seeing? > 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)
[jira] [Commented] (ARTEMIS-4482) Management console becomes unresponsive with ~300 queues/addresses
[ https://issues.apache.org/jira/browse/ARTEMIS-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17782033#comment-17782033 ] Moritz Schmitz von Hülst commented on ARTEMIS-4482: --- Made a video of my tests: Part 1: [^Bildschirmaufnahme 2023-11-02 um 08.27.58.mov] (goes until I add addresses) Part 2: [^Bildschirmaufnahme 2023-11-02 um 08.37.29.mov] (after I have added 300 queues/addresses) Regarding the preferences I just realized they seem to be cached in browser storage. > 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, > 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)
[jira] [Commented] (ARTEMIS-4482) Management console becomes unresponsive with ~300 queues/addresses
[ https://issues.apache.org/jira/browse/ARTEMIS-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17781830#comment-17781830 ] Moritz Schmitz von Hülst commented on ARTEMIS-4482: --- Hey [~jbertram] thanks for the response and help here. I tried what you have suggested and at first it seems that it helped. I set `maxDepth=3` and `maxCollectionSize=1`, update rate to `60 Seconds`. However, locally I still run into the issue that when I refresh and don't wait for the page to load yet, I am able to get into a state where the console doesn't load at all anymore. Sometimes the `Artemis` tab doesn't load (which seems to be a CSS problem though). And perhaps another question right here: Can I set these preferences somewhere in the configuration files? As IaC? > 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: 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)
[jira] [Commented] (ARTEMIS-4482) Management console becomes unresponsive with ~300 queues/addresses
[ https://issues.apache.org/jira/browse/ARTEMIS-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
