I also had a similar issue with performance of Artemis 2.40.0 web console with about 3000 addresses/queues, but had not much time to investigate the issue, gather thread dumps, create a reproducer etc. And we still did not try to migrate any of Artemis instances to 2.40+ (even smaller ones).
пн, 6 окт. 2025 г. в 17:00, <[email protected]>: > Hello Team, > > on an Artemis broker 2.42 with some thousands of queues and topics we can > reproduce the > following case: > open a WebConsole. > > - broker blocked, browser frozen > - 100% CPU for broker process > - This situation lasts longer as the client session keep alive period > (30 sec). Therefore clients terminate the connections. > - additional tasks cleaning up all objects. > > We had a single case, where the broker completely crashed with OOM in such > a situation. > But in most cases the broker survives with all clients gone to another > broker by desaster failover. > Should we avoid WebConsole at all or is there a switch to keep this load > out of the broker? > > Best Regards > > Herbert > ------------------------------ > > *Herbert Helmstreit* > Senior Software Engineer > > Phone: +49 941 / 7 83 92 36 > [email protected] > > www.systema.com > > [image: LinkedIn] <https://www.linkedin.com/company/systema-gmbh/>[image: > Facebook] <https://de-de.facebook.com/SYSTEMA.automation/>[image: XING] > <https://www.xing.com/pages/systemagmbh> > > SYSTEMA > Systementwicklung Dipl.-Inf. Manfred Austen GmbH > > Manfred-von-Ardenne-Ring 6 | 01099 Dresden > HRB 11256 Amtsgericht Dresden | USt.-ID DE 159 607 786 > Geschäftsführer: Manfred Austen, Enno Danke, Dr. Ulf Martin, Jürg Matweber > > P Please check whether a printout of this e-mail is really necessary. > >
