Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COI've rarely seen an unreponsive JVM with single-threaded, high CPU utilization be anything than the Garbage Collector in a panic. Garbage Collection logging will only provide you with confirmation of the collector behavior and an indication of the pattern of heap utilization, to determine the cause you'll need a heap dump and analyze with a tool such as Eclipse MAT (I've lost count of the number of times I've used a heap dump to find a difficult heap or application state issue, they really are invaluable).
      singulars
    2. COActually the GC logging was enabled at that time (we have it on by default), but unfortunately the gc.log file was overwritten when the application was restarted. We'll take care not to delete it next time this happens. I have tried to generate a heap dump out of the core file, but I didn't manage to do it as jmap complains it can't connect to the core file (I'm quite sure I specified the right executable - jsvc). An I agree with you, Eclipse MAT is pure gold! ;-)
      singulars
    3. COAccording to this: http://www.oracle.com/technetwork/java/javase/gc-tuning-6-140523.html#cms.oom the JVM should throw an OOM error at some point if it can't make progress. In our case the JVM was hung for more than 10 minutes and no OOM was thrown. Isn't the fact that kill -3 doesn't trigger a thread dump strange? Or is the VM thread that I mentioned above the one responsible for dumping the stacktraces at the console and since it was so busy with GC-ing it didn't get to do it?
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload