Which Java thread is hogging the CPU?

Identifying which Java Thread is consuming most CPU in production server.

Most (if not all) productive systems doing anything important will use more than 1 java thread. And when something goes crazy and your cpu usage is on 100%, it is hard to identify which thread(s) is/are causing this. Or so I thought. Until someone smarter than me showed me how it can be done. And here I will show you how to do it and you too can amaze your family and friends with your geek skills.

A Test Application

In order to test this, we need a test application. So I will give you one. It consists of 3 classes:

• A HeavyThread class that does something CPU intensive (computing MD5 hashes)
• A LightThread class that does something not-so-cpu-intensive (counting and sleeping).
• A StartThreads class to start 1 cpu intensive and several light threads.

Here is code for these classes:

import java.security.MessageDigest;import java.security.NoSuchAlgorithmException;import java.util.UUID;/** * thread that does some heavy lifting * * @author srasul * */public class HeavyThread implements Runnable {        private long length;        public HeavyThread(long length) {                this.length = length;                new Thread(this).start();        }        @Override        public void run() {                while (true) {                        String data = "";                        // make some stuff up                        for (int i = 0; i < length; i++) {                                data += UUID.randomUUID().toString();                        }                        MessageDigest digest;                        try {                                digest = MessageDigest.getInstance("MD5");                        } catch (NoSuchAlgorithmException e) {                                throw new RuntimeException(e);                        }                        // hash the data                        digest.update(data.getBytes());                }        }}import java.util.Random;/** * thread that does little work. just count & sleep * * @author srasul * */public class LightThread implements Runnable {        public LightThread() {                new Thread(this).start();        }        @Override        public void run() {                Long l = 0l;                while(true) {                        l++;                        try {                                Thread.sleep(new Random().nextInt(10));                        } catch (InterruptedException e) {                                e.printStackTrace();                        }                        if(l == Long.MAX_VALUE) {                                l = 0l;                        }                }        }}/** * start it all * * @author srasul * */public class StartThreads {        public static void main(String[] args) {                // lets start 1 heavy ...                new HeavyThread(1000);                // ... and 3 light threads                new LightThread();                new LightThread();                new LightThread();        }}

Assuming that you have never seen this code, and all you have a PID of a runaway Java process that is running these classes and is consuming 100% CPU.

First let's start the StartThreads class.

$ lsHeavyThread.java  LightThread.java  StartThreads.java$ javac *$ java StartThreads &

At this stage a Java process is running should be taking up 100 cpu. In my top I see:

In top press Shift-H which turns on Threads. The man page for top says:

   -H : Threads toggle        Starts top with the last remembered 'H' state reversed.  When        this  toggle is On, all individual threads will be displayed.        Otherwise, top displays a  summation  of  all  threads  in  a        process.

And now in my top with Threads display turned ON i see:

And I have a java process with PID 28294. Lets get the stack dump of this process using jstack:

$ jstack 289242010-11-18 13:05:41Full thread dump Java HotSpot(TM) 64-Bit Server VM (17.0-b16 mixed mode):"Attach Listener" daemon prio=10 tid=0x0000000040ecb000 nid=0x7150 waiting on condition [0x0000000000000000]   java.lang.Thread.State: RUNNABLE"DestroyJavaVM" prio=10 tid=0x00007f9a98027800 nid=0x70fd waiting on condition [0x0000000000000000]   java.lang.Thread.State: RUNNABLE"Thread-3" prio=10 tid=0x00007f9a98025800 nid=0x710d waiting on condition [0x00007f9a9d543000]   java.lang.Thread.State: TIMED_WAITING (sleeping)    at java.lang.Thread.sleep(Native Method)    at LightThread.run(LightThread.java:21)    at java.lang.Thread.run(Thread.java:619)"Thread-2" prio=10 tid=0x00007f9a98023800 nid=0x710c waiting on condition [0x00007f9a9d644000]   java.lang.Thread.State: TIMED_WAITING (sleeping)    at java.lang.Thread.sleep(Native Method)    at LightThread.run(LightThread.java:21)    at java.lang.Thread.run(Thread.java:619)"Thread-1" prio=10 tid=0x00007f9a98021800 nid=0x710b waiting on condition [0x00007f9a9d745000]   java.lang.Thread.State: TIMED_WAITING (sleeping)    at java.lang.Thread.sleep(Native Method)    at LightThread.run(LightThread.java:21)    at java.lang.Thread.run(Thread.java:619)"Thread-0" prio=10 tid=0x00007f9a98020000 nid=0x710a runnable [0x00007f9a9d846000]   java.lang.Thread.State: RUNNABLE    at sun.security.provider.DigestBase.engineReset(DigestBase.java:139)    at sun.security.provider.DigestBase.engineUpdate(DigestBase.java:104)    at java.security.MessageDigest$Delegate.engineUpdate(MessageDigest.java:538)    at java.security.MessageDigest.update(MessageDigest.java:293)    at sun.security.provider.SecureRandom.engineNextBytes(SecureRandom.java:197)    - locked <0x00007f9aa457e400> (a sun.security.provider.SecureRandom)    at sun.security.provider.NativePRNG$RandomIO.implNextBytes(NativePRNG.java:257)    - locked <0x00007f9aa457e708> (a java.lang.Object)    at sun.security.provider.NativePRNG$RandomIO.access$200(NativePRNG.java:108)    at sun.security.provider.NativePRNG.engineNextBytes(NativePRNG.java:97)    at java.security.SecureRandom.nextBytes(SecureRandom.java:433)    - locked <0x00007f9aa4582fc8> (a java.security.SecureRandom)    at java.util.UUID.randomUUID(UUID.java:162)    at HeavyThread.run(HeavyThread.java:27)    at java.lang.Thread.run(Thread.java:619)"Low Memory Detector" daemon prio=10 tid=0x00007f9a98006800 nid=0x7108 runnable [0x0000000000000000]   java.lang.Thread.State: RUNNABLE"CompilerThread1" daemon prio=10 tid=0x00007f9a98004000 nid=0x7107 waiting on condition [0x0000000000000000]   java.lang.Thread.State: RUNNABLE"CompilerThread0" daemon prio=10 tid=0x00007f9a98001000 nid=0x7106 waiting on condition [0x0000000000000000]   java.lang.Thread.State: RUNNABLE"Signal Dispatcher" daemon prio=10 tid=0x0000000040de4000 nid=0x7105 runnable [0x0000000000000000]   java.lang.Thread.State: RUNNABLE"Finalizer" daemon prio=10 tid=0x0000000040dc4800 nid=0x7104 in Object.wait() [0x00007f9a97ffe000]   java.lang.Thread.State: WAITING (on object monitor)    at java.lang.Object.wait(Native Method)    - waiting on <0x00007f9aa45506b0> (a java.lang.ref.ReferenceQueue$Lock)    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:118)    - locked <0x00007f9aa45506b0> (a java.lang.ref.ReferenceQueue$Lock)    at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:134)    at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159)"Reference Handler" daemon prio=10 tid=0x0000000040dbd000 nid=0x7103 in Object.wait() [0x00007f9a9de92000]   java.lang.Thread.State: WAITING (on object monitor)    at java.lang.Object.wait(Native Method)    - waiting on <0x00007f9aa4550318> (a java.lang.ref.Reference$Lock)    at java.lang.Object.wait(Object.java:485)    at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116)    - locked <0x00007f9aa4550318> (a java.lang.ref.Reference$Lock)"VM Thread" prio=10 tid=0x0000000040db8800 nid=0x7102 runnable "GC task thread#0 (ParallelGC)" prio=10 tid=0x0000000040d6e800 nid=0x70fe runnable "GC task thread#1 (ParallelGC)" prio=10 tid=0x0000000040d70800 nid=0x70ff runnable "GC task thread#2 (ParallelGC)" prio=10 tid=0x0000000040d72000 nid=0x7100 runnable "GC task thread#3 (ParallelGC)" prio=10 tid=0x0000000040d74000 nid=0x7101 runnable "VM Periodic Task Thread" prio=10 tid=0x00007f9a98011800 nid=0x7109 waiting on condition JNI global references: 910

From my top I see that the PID of the top thread is 28938. And 28938 in hex is 0x710A. Notice that in the stack dump, each thread has an nid which is dispalyed in hex. And it just so happens that 0x710A is the id of the thread:

"Thread-0" prio=10 tid=0x00007f9a98020000 nid=0x710a runnable [0x00007f9a9d846000]   java.lang.Thread.State: RUNNABLE    at sun.security.provider.DigestBase.engineReset(DigestBase.java:139)    at sun.security.provider.DigestBase.engineUpdate(DigestBase.java:104)    at java.security.MessageDigest$Delegate.engineUpdate(MessageDigest.java:538)    at java.security.MessageDigest.update(MessageDigest.java:293)    at sun.security.provider.SecureRandom.engineNextBytes(SecureRandom.java:197)    - locked <0x00007f9aa457e400> (a sun.security.provider.SecureRandom)    at sun.security.provider.NativePRNG$RandomIO.implNextBytes(NativePRNG.java:257)    - locked <0x00007f9aa457e708> (a java.lang.Object)    at sun.security.provider.NativePRNG$RandomIO.access$200(NativePRNG.java:108)    at sun.security.provider.NativePRNG.engineNextBytes(NativePRNG.java:97)    at java.security.SecureRandom.nextBytes(SecureRandom.java:433)    - locked <0x00007f9aa4582fc8> (a java.security.SecureRandom)    at java.util.UUID.randomUUID(UUID.java:162)    at HeavyThread.run(HeavyThread.java:27)    at java.lang.Thread.run(Thread.java:619)

And so you can confirm that the thread which is running the HeavyThread class is consuming most CPU.

In read world situations, it will probably be a bunch of threads that consume some portion of CPU and these threads put together will lead to the Java process using 100% CPU.

Summary

• Run top
• Press Shift-H to enable Threads View
• Get PID of the thread with highest CPU
• Convert PID to HEX
• Get stack dump of java process
• Look for thread with the matching HEX PID.

jvmtop can show you the top consuming threads:

    TID NAME                                 STATE     CPU    TOTALCPU     25 http-8080-Processor13                RUNNABLE  4.55%     1.60% 128022 RMI TCP Connection(18)-10.101.       RUNNABLE  1.82%     0.02%  36578 http-8080-Processor164               RUNNABLE  0.91%     2.35% 128026 JMX server connection timeout   TIMED_WAITING  0.00%     0.00%

Try looking at the Hot Thread Detector plugin for visual VM -- it uses the ThreadMXBean API to take multiple CPU consumption samples to find the most active threads. It's based on a command-line equivalent from Bruce Chapman which might also be useful.