Gašper Čefarin created ARTEMIS-5737:
---------------------------------------
Summary: Duplicated jolokia calls on web console's status page
Key: ARTEMIS-5737
URL: https://issues.apache.org/jira/browse/ARTEMIS-5737
Project: ActiveMQ Artemis
Issue Type: Improvement
Components: Web Console
Affects Versions: console-1.3.0
Reporter: Gašper Čefarin
Attachments: artemis new.png, artemis old-1.png,
image-2025-11-02-13-38-00-089.png
This could be part of the problem reported by Herbert Helmstreit (WebConsole on
broker with many queues) on mailing list.
Current implementation makes 27 jolokia calls on status page, while the new one
makesonly 10:
old: !artemis old-1.png|width=1752,height=643!
new: !artemis new.png|width=1757,height=392!
I also checked what's happening here:
{code:java}
const timer = setInterval(getBrokerInfo, 5000)
return () => clearInterval(timer){code}
getBrokerInfo calls artemisService.getBrokerInfo(), which fetches stuff like
Version, HAPolicy, mem usage, uptime ... this was the call with the biggest
payload in my case.
This also fetches all the queue and address names as well, which is not needed
to update the status page, creating unnecessary load every 5 seconds on both
the client and the broker:
!image-2025-11-02-13-38-00-089.png!
There's another thing to consider:
If I understand this correctly, the code executes every 5 seconds and so if
getBrokerInfo does not finish in under 5 seconds, the calls begin to stack ...
--
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
