Forgot to mention - since you know what queues and topics have fast consumers that can keep up with producers, you can always setup nagios alerts (warn/critical) on 'Pending Messages'. I use my broker liveness monitor daemon that periodically performs synthetic transactions against the broker so I can auto-markdown bad apple broker nodes on the client side.
On Feb 7, 2013, at 8:40, Gaurav Sharma <gaurav.cs.sha...@gmail.com> wrote: > Folks - when you notice the broker in a 'stuck' state, please take a thread > and heap dump before killing the broker process and share with devs on here. > > Also: > 1. What broker topology are you using? > 2. How many producers/consumers? > 3. Are you pooling connections, producers, sessions? > 4. How large are your messages? > 5. How many concurrent connections? What is the rate of message flow /second? > 6. Are messages persistent and if so, what store? > 7. What are your system/memory usage settings? How much heap and RAM on > brokers and on clients? > 8. What is the prefetch size? > 9. How are you using the broker - what role is it playing in your system? > Using queues, topics, both? > 10. Have you monitored GC activity on clients and brokers? > 11. What amq transport are you using and via what client? > > There might be more than one factors at play here. Very curious how restarts > are 'fixing' the problem. > > On Feb 7, 2013, at 8:18, Donald Masanz <don.mas...@carters.com> wrote: > >> I took your advice this morning when I noticed that MQ had hung up and was >> able to keep my application running while I restarted MQ. Great tip. Do >> you have a process that monitors MQ and notifies you if it stops processing, >> or do you have to do a manual check? >> >> From: tetoconsusport [via ActiveMQ] >> [mailto:ml-node+s2283324n4662949...@n4.nabble.com] >> Sent: Wednesday, February 06, 2013 4:52 PM >> To: Masanz, Don >> Subject: Re: Stuck Messages >> >> Did you find a solution for this? We are running activemq 5.7 and have had >> this issue as well. If we restart activemq everything works however, we have >> not been able to find the root cause. >> ________________________________ >> If you reply to this email, your message will be added to the discussion >> below: >> http://activemq.2283324.n4.nabble.com/Stuck-Messages-tp4662092p4662949.html >> To unsubscribe from Stuck Messages, click >> here<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4662092&code=ZG9uLm1hc2FuekBjYXJ0ZXJzLmNvbXw0NjYyMDkyfC0yMzQzNTczNA==>. >> NAML<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >> >> >> >> >> -- >> View this message in context: >> http://activemq.2283324.n4.nabble.com/Stuck-Messages-tp4662092p4662985.html >> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
