I'd start by trying to figure out whether what's slow is the broker's
delivery of messages to the ActiveMQ client code or the ActiveMQ client
code's delivery of messages to your code, which is what those JMX stats
would help you figure out.
You say you're not seeing any log lines about slow consum
Thanks.. I’m investigating whether this is slow consumer activity but I
don’t have any log error messages marking them as slow.
On Sun, Mar 1, 2015 at 6:59 AM, Tim Bain wrote:
> Look in JMX to view all the consumers for a queue; for each one, look at
> the dispatched count and see whether it's
Look in JMX to view all the consumers for a queue; for each one, look at
the dispatched count and see whether it's around zero, around your prefetch
buffer size, or somewhere in the middle.
If they're all near zero, that means the broker isn't delivering messages
to the clients' prefetch buffer fa
Hi Kevin,
Knowing how the clients are consuming messages could help, i.e. whether it’s
transactional or not, whether MessageConsumers are being reused/pooled, etc. As
a long shot, I’d try lowering the prefetch limit client side. I’ve had to do
this occasionally to work around inefficient Camel
I’m having a weird situation where ActiveMQ is refusing to send messages to
my consumers.
I have 4 main queues that my consumers receive messages on. I have plenty
of them. They have plenty of CPU, network, etc.
I looked at their stack traces and they’re ALL waiting to receive messages.
ActiveM
