Have you checked the memory use of the process? Use a JMX client (such as jconsole or visualvm) to watch the memory use on the broker until it freezes. Watch permgen space and heap space especially.
High connection counts point to a possible permgen space issue. Most commonly the entire broker only freezes when the JVM is out of memory. If the permgen is running out of space, there may be clients creating and closing connections rapidly - a very bad practice for JMS. Anyway, besides fixing the clients, enabling permgen space garbage collection may work for you (it did for me). -- View this message in context: http://activemq.2283324.n4.nabble.com/Hung-ActiveMQ-broker-and-processes-are-blocking-tp4675874p4676011.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
