Hi Blaze, in thread3.out I found this [1], the id 14274 corresponds to the
one reported by top. From the first glance looks like [1] is GC thread. So
I'm starting to think that 100% CPU is caused by GC. You can try to monitor
GC cycles and memory consumption (for ex. using jvisualvm). WBR, Alexey. [1]
----------------- 14274 ----------------- 0x00a1f9c9
_ZN13instanceKlass19oop_follow_contentsEP7oopDesc + 0x119 0x00b1aa21
_ZN9MarkSweep12follow_stackEv + 0x31 0x00c3ef87
_ZN8Universe7oops_doEP10OopClosureb + 0x17 0x00bc2752
_ZN10SharedHeap20process_strong_rootsEbbNS_14ScanningOptionEP10OopClosureP15CodeBlobClosureP16OopsInGenClosure
+ 0x2a2 0x009f4cfb
_ZN16GenCollectedHeap24gen_process_strong_rootsEibbbN10SharedHeap14ScanningOptionEP16OopsInGenClosurebS3_
+ 0x5b 0x009f796f _ZN12GenMarkSweep17mark_sweep_phase1Eib + 0x7f 0x009f7f65
_ZN12GenMarkSweep19invoke_at_safepointEiP18ReferenceProcessorb + 0x105
--
[Message sent by forum member 'oleksiys']
View Post: http://forums.java.net/node/892403