This looks strongly like a bug in your consumer code, not a problem with ActiveMQ. You're using CLIENT_ACKNOWLEDGE mode (<property name="sessionAcknowledgeModeName" value="CLIENT_ACKNOWLEDGE"/>), which means that if you have a bug that causes you to not ack your messages (due to logic errors, exceptions, infinite loops, thread death, long-running calls to external services, etc.), this behavior is exactly what you'd see. Based on what you've shared so far, that seems like the most likely explanation.
In addition to the thread dump (as Raul said, from the consumer, not the broker), look at your consumer code for any of the errors I listed above. Tim On Aug 19, 2016 2:45 AM, "Raul Kripalani" <r...@evosent.com> wrote: > Could you please take a thread dump of the consumer? > > --- > Raúl Kripalani > linkedin.com/in/raulkripalani | evosent.com > <http://evosent.com/?utm_source=email&utm_medium=email&; > utm_campaign=evosent_raul> > | blog: raul.io > <http://raul.io?utm_source=email&utm_medium=email&utm_ > campaign=evosent_raul> | > skype: raul.fuse > > On Fri, Aug 19, 2016 at 4:06 AM, softwbc <soft...@163.com> wrote: > > > This is no problem to get the dump log ( jstack.log > > <http://activemq.2283324.n4.nabble.com/file/n4715645/jstack.log> ) > > > > I see there is a queue does not consume message > > <http://activemq.2283324.n4.nabble.com/file/n4715645/1.jpg> > > > > > > > > -- > > View this message in context: http://activemq.2283324.n4. > > nabble.com/activemq-3000-messages-can-not-be-received- > > tp4715396p4715645.html > > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > > >
