The broker wasn't at its memory limit at the time when this had occurred, but it wouldn't allow for JMX connections. I'd assume
I was able to collect a heapdump before ActiveMQ was restarted and it does mention the Server Transport thread mentioned earlier. I'm not able to identify the thread to the stacks in the thread dump: <http://activemq.2283324.n4.nabble.com/file/n4676637/2014-01-22_14_37_06-Eclipse_Memory_Analyzer.jpg> -- 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-tp4671744p4676637.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
