It's hard to know what's causing the problem from the description. Can you perform java memory-leak diagnosis?
Capturing a heap dump after running for a while, or perhaps two with a few hours between them, and then opening in your favorite heap-dump analysis tool. Yourkit is a good one for finding memory leaks. VisualVM can do the job, but can be harder to work through. Use the "calculate retained sizes" feature of such a tool to get a good feel for the largest retainers of memory. -- View this message in context: http://activemq.2283324.n4.nabble.com/Memory-Leak-problem-after-upgrade-from-5-5-1-to-5-10-tp4685103p4685126.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
