With any problem involving message delivery, the first question is which consumers are connected and what they're doing. JMX will let you see who's connected; I use JConsole's MBeans tab to find the queue and then look at how many consumers are under it when you expand that tree node. If you have consumers but their prefetch buffers are full, it means they're not keeping up with the rate messages are being sent. If they're using subscription filters, then you need to make sure that each message matches at least one consumer. There are other possibilities, but it all depends on what the JMX stats tell you.
Tim On Dec 23, 2016 1:38 AM, "fcbman" <fcb...@gmail.com> wrote: > Hello Experts, > I'm new to activeMQ and hence please forgive my ignorance (sometimes it is > a > blessing). > It seems like the messages are getting in the queue, but or no one gets > them, or something is stuck. > If I restart the activemq, then all works fine and issue starts after > couple > of hours... > I'm not sure how I can debug such case and see which messages there are and > who should get them. > I've enabled the JMX and I can connect the console and execute this: > activemq:bstat internalBroker > Which will give me lots of data which I got lost from :) > > Is that the correct way to debug it? if so - what should I look in the > output? > Is there any other cli command that might assist? GUI tools? > > We are on linux RH 5/6 and activemq 5.7.0.1. > > Appreciate any reply that might assist :) > Thanks you. > > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/queue-gets-full-and-seems-stuck-how-can-I- > debug-such-issue-tp4720742.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
