there is a direct correlation between dispatch attempts and message
enqueues, what I think you are seeing is the broker trying to dispatch each
message in turn and each time determining that all consumes are full. The
spike should quickly dissipate once one attempt to dispatch each message is
made.
BTW, I forgot to mention one possibly key piece of info. The consumers run
on a different server. ActiveMQ runs on its own dedicated server. So it's
using TCP, not VM, in case that matters.
dcheckoway wrote:
>
> I'm experiencing an issue with ActiveMQ 5.3.1 broker. Here's my setup:
>
> - 1
