Java Thread Dump Analyzer

A raw thread dump from a stuck JVM is thousands of lines long. This analyzer parses it and surfaces what matters: deadlocks, which lock everyone is waiting on, and what the busy threads are doing.

What a thread dump is

A thread dump is a snapshot of every thread in a Java process at one instant — its name, state (RUNNABLE, BLOCKED, WAITING, TIMED_WAITING), the monitors it holds, the monitor it is waiting for, and its full stack trace. You get one with jstack <pid>, jcmd <pid> Thread.print, or by sending kill -3 to the process (the dump goes to stdout). Application servers like Tomcat and Spring Boot Actuator can also produce one on demand.

What the analyzer shows

Deadlocks: cycles where thread A holds lock X and waits for Y while thread B holds Y and waits for X. The JVM reports these explicitly and the tool highlights them first. State summary: counts of threads per state — hundreds of BLOCKED threads point to contention, hundreds of RUNNABLE threads on the same frame point to a CPU hot spot. Lock contention: which monitor is most waited on and which thread currently owns it. Thread pools: grouped by name prefix (http-nio-*, pool-3-thread-*) so you can see whether a pool is exhausted.

How to read the result

Take three dumps 5–10 seconds apart. A thread that is RUNNABLE in the same frame across all three is genuinely busy there; one that is WAITING on a queue poll is idle and healthy. If request threads are all BLOCKED on one lock, find the owner thread and look at its stack — that is the real bottleneck. If they are all waiting on a socket read, the problem is a slow downstream service, not your code.

How to use it

  1. Capture a dump: jstack <pid> > dump.txt (or jcmd <pid> Thread.print).
  2. Drop the file onto the analyzer or paste the text. Dumps from OpenJDK, Oracle JDK, Amazon Corretto, Azul and IBM Semeru are recognised.
  3. Review the deadlock panel, state breakdown and contention list; expand any thread to read its stack.

What a blocked thread looks like

A single thread entry from a dump:

"http-nio-8080-exec-42" #87 daemon prio=5 os_prio=0 tid=0x00007f… nid=0x3e1a waiting for monitor entry
   java.lang.Thread.State: BLOCKED (on object monitor)
        at com.example.cache.LocalCache.get(LocalCache.java:88)
        - waiting to lock <0x00000006c1a2f3d0> (a java.util.HashMap)
        at com.example.web.ProductController.show(ProductController.java:51)

This request thread is blocked trying to enter a synchronized block guarding a HashMap. The analyzer will tell you which thread holds 0x…f3d0 and how many others are queued behind it.

Common use cases

Frequently asked questions

Is my thread dump uploaded?

By default parsing runs entirely in your browser. The optional backend upload is only used if you explicitly configure a backend URL for very large files.

Which formats are supported?

HotSpot-style dumps from jstack, jcmd Thread.print, kill -3 output and Spring Boot Actuator /threaddump text output. IBM/OpenJ9 javacore files are partially supported.

Why are so many threads WAITING or TIMED_WAITING?

That is usually normal — idle pool workers wait on a queue, schedulers sleep between runs. Focus on BLOCKED threads and on RUNNABLE threads that repeat the same frame across multiple dumps.

How many dumps should I take?

At least three, several seconds apart. A single dump shows a moment; comparing dumps shows what is stuck versus what is just passing through.

Related tools

Explore all developer tools →