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 clients. http://activemq.apache.org/what-is-the-prefetch-limit-for.html <http://activemq.apache.org/what-is-the-prefetch-limit-for.html>
Regards, Tim > On 1 Mar 2015, at 1:32 pm, Kevin Burton <bur...@spinn3r.com> wrote: > > 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. > > ActiveMQ has about 7000 messages in these 4 queues that it’s just trickling > out to the consumers. VERY slow rate. > > The box it’s running on is fine. ActiveMQ has plenty of memory, isn’t > GCing. I also looked at its stack traces and nothing weird here. > > It’s just not sending at a very fast rate. > > Now, if I restart all my daemons, including ActiveMQ , everything works > fine for about 1-2 hours, then I get to this stall point again. > > I’ve read about the slow consumers. I don’t have any log warnings for this > so I don’t think that’s a problem. (plus these are queues). > > Anything else I should look into? > > -- > > 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>
