Next time it happens, see if you can browse the messages on the queues. That might indicate whether the problem is the data store (if you can't browse the queues) or something more localized like the dispatch thread (if you can).
Also, you need to take thread dumps and/or use a profiler (both is best) to let us figure out what the different threads are doing. I'm out of ideas based on what information you've got at the moment, so hopefully seeing what the threads are doing will help narrow in on the problem. Tim On Aug 22, 2015 6:50 PM, "Richard Sinek" <rsi...@intouchgps.com> wrote: > There is a specific queue that gets the scheduled messages and generally a > single consumer thread on that queue. That consumer is part of the same > application that is pulling from all the other queues. > > We don't use selectors on any queue, of which there are 15, nor do we have > any destination based GC. > > The web console is fully responsive during the events, I have not actually > tried browsing. > > The issue is very repeatable, in many cases happening multiple times per > day. Often it gets progressively worse and restarting the consumers usually > helps. > > > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/AMQ-pauses-sending-to-consumers-tp4701242p4701309.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
