It looks like this is a function of queue size.. if it grows large enough, eventually, it seems, ActiveMQ stops dispatching messages to the consumers.
On Wed, Apr 15, 2015 at 6:55 PM, Kevin Burton <[email protected]> wrote: > I have a very strange bug I’m trying to track down. > > I have a very loaded ActiveMQ box (8 of them actually)… for the most part > it’s working very well. > > However, I recently noticed that some of our queues aren’t actually doing > any work. Other queues are performing just fine. In fact, the vast > majority of them are performing fine. > > It’s just a few of them each with the same name. > > I’ve tried restarting both of my apps that consume my message, only to > find the exact same behavior. > > The code is basically just not reading new messages sent to these given > queues. > > I can’t restart the broker because we’re using the memory store for > performance reasons. > > I can browse them manually … the messages are there. JMX reports > thousands of messages waiting to be executed. > > One theory I have is maybe the ActiveMQ connection isn’t properly handing > messages to all my consumers. The box is rather loaded. I’m also calling > receiveNoWait.. to read these queues. So perhaps some buffer is being > filled up with other queues or some of my connections aren’t being serviced? > > Thoughts? > > -- > > Founder/CEO Spinn3r.com > Location: *San Francisco, CA* > blog: http://burtonator.wordpress.com > … or check out my Google+ profile > <https://plus.google.com/102718274791889610666/posts> > <http://spinn3r.com> > > -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
