Hi,
we have Artemis 2.20.0 cluster which is used by external producers/consumers.
Every such producer/consumer pair represents different commercial client
(company) so we are using one queue per client to separate their messages. Our
developers are using auto-created JMS address/queue combination to serve these
clients. These auto-created queues are durable as per Artemis documentation.
Now, the issue is we have thousands of these clients so naturally we have
thousands of addresses and almost the same amount of queues in our cluster.
When trying to access Hawtio console the broker uses all CPU and RAM available.
Console is really slow and sometimes even crashes the broker. Is this a known
issue?
This is on completely idle system with just couple of consumers attached at any
given time (addresses are precreated in advance). The machines are multi-core
Xeons with 8 GB of RAM. Address memory is barely used ~12 MB.
Or maybe we are doing something wrong? Maybe switching to temporary queues
would help?
--
Best Regards,
Vilius Šumskas
Rivile
IT manager
+370 614 75713
