[
https://issues.apache.org/jira/browse/ARTEMIS-2606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17026092#comment-17026092
]
Sebastian T commented on ARTEMIS-2606:
--------------------------------------
[~jbertram] I am currently manually patching the class file for our broker
installation and it works as expected.
Regarding ARTEMIS-2091, I guess it could not even be implemented before. AFAIK
only as of Hawt.io 2.8 custom plugins are actually possible. This was
implemented via [https://github.com/hawtio/hawtio/pull/2600]
[~tadayosi] It would be great if you can backport the fix and create a hotfix
release. I guess migrating a plugin from Hawt.io 1 to 2 is not just copying and
pasting the files to new locations but means reimplementing the plugin and thus
it will take some time/effort before the Artemis web console gets migrated.
> Artemis Admin Web Console not loading on server with many queues
> ----------------------------------------------------------------
>
> Key: ARTEMIS-2606
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2606
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Web Console
> Affects Versions: 2.11.0
> Environment: Artemis 2.11.0 on AmazonLinux 2 with Amazon Corretto JDK
> (but also reproducable on Windows with OpenJDK)
> Reporter: Sebastian T
> Priority: Critical
>
> We have a high number of queues 10.000+ on one of our Artemis cluster. Now
> the Artemis admin UI is not responding at all (blank screen).
> I did some testing and saw that when I access a server with 500 queues, the
> console downloads a 8.5MB JSON file from the server to the browser, when I
> have 3000 queues that JSON file is already 35MB large.
> This is the HTTP Request:
> https://<ROOT_URL>/jolokia/?maxDepth=9&maxCollectionSize=50000&ignoreErrors=true&canonicalNaming=false
> Request Method:POST
> Request Body:
> \{"type":"exec","mbean":"hawtio:type=security,name=RBACRegistry","operation":"list()"}
> I suspect the problem is related to the fact that Artemis creates MBean
> objects for each address and queue and when all MBean information are
> downloaded by Hawt.io via Jolokia.
> We used RabbitMQ before and had no issues with their admin UI while
> administering 30.000+ queues.
> Any suggestions regarding temporary workarounds are appreciated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
