That sounds like the typical Java memory leak. If so, it should be easy to track down since it sounds easily reproduced.
I recommend grabbing a couple of heap dumps a few hours, or days, apart, and comparing. JVisualVM can help analyze the heap dump. YourKit is even better. -- View this message in context: http://activemq.2283324.n4.nabble.com/Consumer-is-hung-and-Heap-Memory-limit-is-reaching-Maximum-tp4684926p4684955.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
