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

Sebastian T commented on ARTEMIS-2606:
--------------------------------------

I changed priority to critical as we are seeing very high memory allocations 
because of this issue that affect broker operation.

My PR for the Hawt.io project got merged into the 2.x stream. Maybe you have a 
possibility to somehow integrate the fix for the RBACRegistry into the artemis 
distribution.

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

Reply via email to