We had this problem as well. We resolved it by sending a DISCONNECT command before our stomp client quits. If you don't send the DISCONNECT command, the connections will continue to add up in ActiveMQ until it crashes with the error you got. This behavior seems to have started with ActiveMQ 4.1, since we didn't have this problem with older versions.
-- View this message in context: http://www.nabble.com/ActiveMQ-%3A-java.lang.OutOfMemoryError%3A-unable-to-create-new-native-thread-tf4099069s2354.html#a11658208 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
