Try taking a stack dump of the process once in a while and look at the list of threads. There may be a leak, such as a connection leak, that needs to be addressed. Using the stack dump, it should be easy to identify which threads are being created and sticking around for a long time.
-- View this message in context: http://activemq.2283324.n4.nabble.com/java-lang-OutOfMemoryError-in-consumer-application-tp4691751p4691790.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
