Posted by boris_petrovic
on January 9, 2008 at 2:17 AM PST
I found very annoying GC trace in which GC events register about 20-30 ms, but Total stopped time trace showed 42.7 seconds!!!.
Does anybody have similar experience. I am trying to understand is there wrong "total time trace " gone when gc event took only 35msec.
Application trace below GC trace proves that long pause really happened
Siemens Fujitsu RX300 Dual Core Intel(R) Xeon(TM) MP CPU 3.00GHz
Linux version 22.214.171.124-0.8-bigsmp
-Xmx640m -Xms640m -XX:MaxPermSize=256m -XX:+UseConcMarkSweepGC -XX:+HeapDumpOnOutOfMemoryError -XX:+PrintGCApplicationStoppedTime -XX:+PrintGCDetails -XX:+PrintGCTimeStamps
Total time for which application threads were stopped: 0.0235980 seconds
6459.777: [GC 6459.777: [ParNew: 8063K->0K(8128K), 0.0351210 secs] 240456K->233461K(655296K), 0.0355370 secs]
Total time for which application threads were stopped: 42.7288190 seconds
18:33:33,821 WARN [HibernateTemplate] Long commit time: 42780ms for com....