Without looking at the stack trace carefully, problems getting stack traces is often seen with a memory leak or overloaded broker (i.e. running out of heap or permgen space).
Can you connect jconsole or visualvm to the broker and check the heap and permgen space when the problem occurs? If you want to capture JVM stats to a text file, jstat is good for that. -- 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-tp4671744p4676604.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
