How to Detect and Diagnose Java Deadlocks Using jstack, ThreadMXBean, and Online Tools

The article introduces the problem of Java deadlocks and asks how developers can locate or proactively discover them during development and production.

Locating deadlocks with jstack

By combining the command‑line utilities jps and jstack , you can obtain a thread dump that reveals deadlock information. The last line of the jstack output typically indicates the presence of a deadlock.

Locating deadlocks with ThreadMXBean

Java provides the ThreadMXBean monitoring interface, which includes the method findDeadlockedThreads() to detect deadlocked threads programmatically.

Example deadlock diagram:

Using ThreadMXBean to detect deadlocks and print related information:

Output of deadlock‑related information:

Locating deadlocks with online tools

FastThread is an online tool that provides a graphical interface for analyzing thread‑dump files from production environments, showing CPU usage, stack depth, and the most frequently invoked methods.

JStack Review is another online utility that visualizes thread dumps without storing data in the cloud, grouping threads by state and separating stack‑based threads from others, which is crucial for distinguishing internal processes.

How to fix deadlocks

In production, the common practice is to quickly take the problematic service offline from the service registry while preserving the current state, then use the above analysis tools to determine the root cause. Ultimately, preventing deadlocks requires disciplined coding practices such as lock ordering and avoiding circular lock dependencies.

Conclusion

If a deadlock occurs, the article provides several methods for locating and fixing it, ranging from command‑line utilities to Java APIs and convenient online analysis platforms.