Java 8u20 kernel (stream dump missing stack trace)

I recently used jvisualvm and jstack to analyze the tomcat Java 8u20 core dump. For most threads, I can see the full stack trace, for example.

Thread 21234: (state = BLOCKED)
 - sun.misc.Unsafe.park(boolean, long) ...

But for the current thread (the one that causes the core dump) there is no stack trace, and all I see is:

Thread 28888: (state = IN_JAVA)

I found the following explanation IN_JAVA:

  • NEW: only start, i.e. upon initialization.
  • IN_NATIVE: Executed in native code.
  • IN_NATIVE_TRANS: Corresponding transition state.
  • IN_VM: Run in a virtual machine.
  • IN_VM_TRANS: Corresponding transition state.
  • IN_JAVA: Running in Java or in code is a stub.
  • BLOCKED: Blocked in vm.
  • BLOCKED_TRANS: Corresponding transition state.

The log he_errshows a method from java that calls into the native VM code, but I'm interested in the rest of the java side stack.

, !

+4

All Articles