Profile Image
Muhammad Sohail Iqbal

high CPU usage issue on our application server (weblogic server)

We are facing high CPU usage issue on our application server (weblogic server). As per thread dump, analyzed using fasthread.io it shows that CPU spike is due to log rotation (Under heavy load, log files starts rotating within 2 mins). While looking at CPU usage using Top -H -b -p [pid] command it shows that it is due to 

"VM Thread" os_prio=0 tid=0x00007f7414320800 nid=0x13a9d runnable 

Need your input.

 

 

Report URL - https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMjIvMDMvMTYvLS1PQkRYTWFuYWdlZFNlcnZlcl8xX3RocmVhZF9kdW1wcy50eHQtLTEwLTQxLTQ3

  • highcpuusage

  • weblogicserver

  • topcommand

Please Sign In or to post your comment or answer

Profile Image

sainath

Hello Sohail,

 

Fantastic! that you are looking at top -H output along with the thread dump. This is the exact direction to identify CPU related problems. But can you do one more step, please create a zip file with the thread dump and top -H output and upload the zip file to fastthread.io. fastthread.io will analyze both outputs and present the threads that are causing CPU to spike related problems under the CPU | Memory section in the generated report as in the below screenshot:  

 

 

Profile Image

Ram Lakshmanan

Hello Muhammed!

 

 

 Inorder to accurately point the lines of code causing the CPU spike, you need to analyze not only thread dumps but also 'top -H -p {PID}' command output, where {PID} is your Java application's process Id which is experiencing CPU spike. When you issue this ‘top’ command with given arguments, it will list all the threads running in the application and amount of CPU each one of the thread consume. Once you have both the data, you can identify high CPU consuming thread and lines of code they are executing.

 

 You can use the open source yCrash script which will capture 360-degree application level artifacts (like GC logs, 3 snapshots of thread dumps, heap dumps) and system level artifacts (like top, top -H, netstat, vmstat, iostat, dmesg, diskusage, kernel parameters...). Once you have these data, either you can manually analyze them or upload it to yCrash tool. Tool analyzes all these dataset and generates an instant root cause analysis report pointing out exact line of code causing the CPU spike. Here is more detailed information on how to diagnose high CPU spike.

Got something else on mind? Post Your Question

Not the answer you're looking for? Browse other questions tagged
  • highcpuusage

  • weblogicserver

  • topcommand