I just took a stack trace from my box and I'm seeing this: Thread 7: (state = BLOCKED)
Thread 6: (state = BLOCKED) - java.lang.Object.wait(long) @bci=0 (Compiled frame; information may be imprecise) - java.lang.ref.ReferenceQueue.remove(long) @bci=44 (Compiled frame) - java.lang.ref.ReferenceQueue.remove() @bci=2 (Compiled frame) - java.lang.ref.Finalizer$FinalizerThread.run() @bci=36 (Compiled frame) Thread 5: (state = BLOCKED) - java.lang.Object.wait(long) @bci=0 (Compiled frame; information may be imprecise) - java.lang.Object.wait() @bci=2, line=503 (Compiled frame) - java.lang.ref.Reference$ReferenceHandler.run() @bci=46 (Compiled frame) I guess I'm not sure what would be blocking. On Fri, Dec 5, 2014 at 4:54 PM, artnaseef <[email protected]> wrote: > Double-check that the consuming processes are trying to consume messages. > > Looking at a stack trace should do the job. Look for a thread waiting to > receive a message. If none can be found, then the consumers may be too > busy > doing other things to pull the messages. > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Messages-Stuck-in-Queue-tp4688438p4688453.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
