I'm much more familiar with debugging the broker than the client, so I don't know exactly how to look into the client to see what state it's in (whether the missing messages are sitting in memory or were never received, what the threads are doing, etc.). I'd start by taking a thread dump and a memory dump of the problematic consumer to see if you can figure that out; if those don't yield any insight, I'd try attaching a debugger to the client (which means you have to have enabled the debug port before you started the consumer) and looking for good places in the ActiveMQ client code to set breakpoints that will show you what happened to the messages. (You'll have to look for the right places to put breakpoints; I don't know them, so you'll need to look at the ActiveMQ client code and pick ones you think make sense.)
Does anyone else have any suggestions for how to debug client problems? (Are there JMX stats available on the client? I've never thought to check before now, and won't be able to till next week.) BTW, was this failure correlated with the NFS issues and failure of the master to yield that you posted about around the same time? Tim On Apr 29, 2015 5:45 AM, "khandelwalanuj" <[email protected]> wrote: > Hi, > > I forgot to mention one point. We recently upgraded to ActiveMQ-5.11.1. And > only after this upgrade, we saw this issue. > > We have encountered this twice. Can some one please check or atleast let me > know if there were some changes related to this in 5.11.1 > > Details: > > Suddenly a consumer stop receiving messages. And in jconsole the > messages > were considered as inflight.(awaiting acknowledgement) > > It happened for durable as well as no-durable subscriber. > > Thanks, > Anuj > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/ActiveMQ-topic-Messages-are-not-delived-to-a-consumer-tp4695554p4695853.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
