Find out how to troubleshoot the most CPU-intensive threads in your Web project on the LIUNX server

Here is a summary of the steps to find the thread resource consumption problem for Linux, Sun (Oracle) JDK, in Linux, when the Java process is found to occupy a high CPU resource, and want to further find out which Java thread is consuming CPU resources, Follow these steps to find:

First step: Log in to the LIUNX server where the Web service resides, and use the top command to get the CPU usage of Java

Step Two:

As shown, the process ID of Java is ' 3260 ', and the next step is to monitor all threads in this process separately with the top command: Top-p 3260-h

Step Three:

As shown in Linux, all Java internal threads actually correspond to a process ID, which means that the Sun JVM on Linux maps threads in Java programs to operating system processes, and we see that the process ID that consumes the most CPU resources is ' 3740 ', This process ID corresponds to the ' Nid ' (' n ' stands for ' native ') in the Java thread information;

Fourth Step:

To find out exactly which specific code occupies so many resources, first use Jstack to play the current stack of information into a file, such as Mystack.log:jstack 3260 > Mystack.log

Fifth Step:

Convert 3740 to 16 in e9c, find the nid=oxe9c thread in the Mystack.log file, and then troubleshoot the code in that thread

Find out how to troubleshoot the most CPU-intensive threads in your Web project on the LIUNX server