Hi All, I have created a project with sample configuration files to reproduce the slow loading of the management console: https://github.com/alexander-milovidov/artemis-slow-console-reproducer
To make the management console work much worse in an isolated environment, I had to create 2000 users, each user is assigned to 4 different roles, created 1000 addresses with anyast queues, and set permissions for each address to its roles. I also set permissions to corresponding DLQ queues. It takes about 2 minutes to load the management console in this configuration. During the opening of the management console with the single user, the JVM metric jvm_gc_memory_allocated_bytes_total rises from 0 to approx. 1.20 Gb/second and reduces after loading. Unfortunately, I didn't reproduce other problems that we have: - excessive garbage collection and high CPU usage; - blocked threads and unresponsive message broker; - slow loading of the list of queues in the Queues tab; - some users (very rarely) complain that they wait for 10-30 minutes to log on to the console which usually opens in 10 seconds. I can also add jinja2 templates of these files (and ansible role/playbook to create files from template) if someone needs. ср, 25 мар. 2026 г. в 19:39, Alexander Milovidov <[email protected]>: > Hello! > > пн, 23 мар. 2026 г. в 10:58, Grzegorz Grzybek <[email protected]>: > >> Can we check (roughly) what is your RBAC configurations? >> >> > There's about 3000 addresses and 4000 queues. The number of distinct roles > in the management.xml is about 750. > Each ACL for an address has 12 access methods (browse*, send* etc.) with > 4-8 roles. > > I plan to create a reproducer with templated configuration files which > creates N addresses with queues, N*2 users with different roles, and > assigns permissions for roles to each address (amq, read-only role and > full-access role) in management.xml. I'll be back with the results. >
