Zoran Avtarovski wrote > 5. Garbage collector time spikes to 24.0. I think with JavaMelody it means > that GC took 24% of of the CPU??
Yes, 24% in % GC time in JavaMelody means that 24% of the CPU. And this is a lot, if longer than a few seconds. Zoran Avtarovski wrote > So I think our issues are related to GC. Is there a way to trigger more > frequent GC which will hopefully be less resource intensive? Triggering frequent GC is a bad idea in general. Zoran Avtarovski wrote > And why have the memory usage levels not recovered? Take a heap dump as said by Chuck, then use Memory Analyzer Tool. Without a heap dump, you can also open the heap histogram in your JavaMelody reports to have a first look, Here is an example in the demo: http://demo.javamelody.cloudbees.net/monitoring?part=heaphisto For analysis of GC trends, you can enable the GC logs of the JVM and use HPJMeter tool. But at the moment, you already know that the memory was not good, so having the trends may be for a later time. Emeric -- View this message in context: http://tomcat.10.n6.nabble.com/Help-in-diagnosing-server-unresponsiveness-tp4993508p4993829.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
