Hi Tim, Thanks for the reply. If I force a full GC, memory usage does not drop. I'm not actually not using all of my memory. Execution is slowing down to the point that messages are timing out (presumably due to excessive GC). I increased the size of my JVM and the change had no effect. For some reason, memory usage repeatedly shoots up to around 750 MB and then drops back to around 100. This cycle can repeat up to 15 times per minute. See image below:
<http://activemq.2283324.n4.nabble.com/file/n4702191/cpuMem.png> So I'm thinking the application is doing something that continually increases memory usage but, if that is the case, why wouldn't it be an issue with Hornet? I'll look into the DeserializerCache. I have no idea how the caching behavior is configured. Unfortunately I'm new to the team (and an intern) so I'm not familiar with the relatively large and complex application (24,000 classes). Thanks. -- View this message in context: http://activemq.2283324.n4.nabble.com/Garbage-collecter-out-of-memory-tp4702160p4702191.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
