That makes sense. Thanks for sharing the resolution to the problem.
Tim
On Thu, May 7, 2020, 8:23 AM bstrange wrote:
> I've finally figured out what was causing this. Viewing the contents of a
> queue by clicking the queue name in the browser interface will spawn a
> consumer to view all of tha
I've finally figured out what was causing this. Viewing the contents of a
queue by clicking the queue name in the browser interface will spawn a
consumer to view all of that data. The more messages in the queue the longer
the cpu spike will last. These consumers don't actually consume the
messages;
If these are consumers on a queue, are they consuming the queue's messages
such that your real consumers don't get all of them? Or are all of the
messages still on the queue despite these consumers having received a
million messages (per your screenshot in your original message)?
How often do thes
The high load could be caused by the phantom consumers and not the other way
around. I've only been able to duplicate the issue once in testing.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
It's a standalone broker. We don't have any networked brokers. These
consumers aren't any we created. They're created on their own and go away on
their own.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
Is this on a standalone broker, or are you running a network of brokers?
Might these consumers be the ones for one broker in a network of brokers to
pull messages from another?
Tim
On Thu, Apr 30, 2020, 1:32 PM bstrange wrote:
> I'm running ActiveMQ 5.11.1 and have two consumers on a queue. If
I'm running ActiveMQ 5.11.1 and have two consumers on a queue. If something
causes the load on the server to spike additional phantom/ghost/auto-created
consumers are created by activemq. These consumers are named the same as the
host when none of the other consumers exist on this host. Does anyone
