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


Reply via email to