For the broker memory - is that looking at the Heap Size and Permgen Size, checking for broker producer-flow-contorl-messages, or something else?
Not being able to connect JMX is a typical symptom of a JVM that's out of Heap or Permgen space. If you connect jconsole, visualvm, or the like before the problem occurs, it will be possible to see the memory status at the time of the problem. The following JVM option can help with detecting out-of-memory conditions: -XX:+HeapDumpOnOutOfMemoryError -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-5-5-1-Connections-stuck-in-CLOSE-WAIT-state-reaching-file-descriptor-limit-tp4671744p4676653.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
