The most common cause of message flow stopping is slow consumption leading to exhaustion of the broker's resources.
Things to check: - Broker memory usage - Broker store usage - ActiveMQ log file (check for producer flow control or resource usage messages) BTW, it is critical with any ActiveMQ installation to ensure consumption >= production always. Short bursts do happen and can be handled, but ultimately, you really never want to be in a situation in which consumption is less than production for a long time. And, when it is known that a burst of production will outpace consumption, it's important to understand the numbers and sizes of messages that will be in the backlog to ensure the broker's memory and store settings can handle it. -- View this message in context: http://activemq.2283324.n4.nabble.com/Activemq-froze-and-msgs-dont-get-processed-tp4680313p4680318.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
