activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gaurav Sharma <>
Subject Re: Finding a hung consumer
Date Tue, 25 Sep 2012 20:56:51 GMT
What does the jmx dashboard show under network, connections, topics,
queues, etc? By default, it is at
http://<master-broker-host>:8161/admin Also, if the app is oome-ing,
might want to take periodic thread dumps and inspect what's going on.
Other areas include inspecting gc logs, io/netstat-ing, heap sizing,
jvm/jit compiler bugs, etc. And ack modes are set on the Session. We
don't know your messaging topology, persistence, network config et al.
So, the suggestions above are a bit generic.

On Sep 24, 2012, at 11:59, kureckam <> wrote:

> We have an application that sometimes runs out of memory. It has five topics
> that multiple consumers and producers interact with. I believe that one of
> the consumers may be getting hung causing ActiveMQ to hang on to the
> messages and fill the buffer. I would like to know if there is a way to
> determine which consumer might be hanging. I also thought that setting
> timeToLive on the producer would release the unacknowledged messages after
> the timeout occurred but that doesn't seem to be the case. Is there a way to
> prevent the buffer from overflowing?
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at

View raw message