I’m trying to diagnose a long term memory leak with ActiveMQ. Basically , my app runs fine for about a week or so, then goes to 100% CPU doing continually full GCs back to back.
No work is done during that period. I have a large number of sessions to the AMQ box, but things are fine on startup. It’s entirely possible that y app isn’t releasing resources, but I”m trying to figure out the best way to track that down. I’m using org.apache.activemq.UseDedicatedTaskRunner=false so that thread pools are used. Which apparently can cause a bit of wasted memory. I have a heap snapshot. I loaded that into the Eclipse Memory Analyzer and didn’t see any obvious candidates but of course I’m not an expert on the ActiveMQ code base. Are there any solid JMX counters I can track during this process? Number of sessions? etc. -- Founder/CEO Spinn3r.com Location: *San Francisco, CA* blog: http://burtonator.wordpress.com … or check out my Google+ profile <https://plus.google.com/102718274791889610666/posts> <http://spinn3r.com>
