A JDK 26 commit replaced reading /proc with a Linux-specific clock_gettime bit manipulation, cutting ThreadMXBean.getCurrentThreadUserTime() latency from 11 µs to 279 ns (40x, 400x under contention), illustrating the "abstraction tax" of portable standards.
This article explains what a Java thread dump is, describes multiple ways to generate it—including JDK command‑line tools like jstack and jcmd, OS signals such as kill ‑3, and programmatic access via ThreadMXBean—provides syntax, options, examples, and recommendations for choosing the appropriate method.
This article explains how to locate Java deadlocks by using command‑line tools such as jps and jstack, the ThreadMXBean API’s findDeadlockedThreads method, and online utilities like FastThread and JStack Review, while also offering guidance on preventing and fixing deadlocks in production.
