Problem: the CPU on the system is pegged to 100% and see application slowdown, and need to trace what is casing this behavior.
Problem Analasys:
In order to properly troubleshoot the high CPU condition Operating System commands are a key to identify the root cause
Please use the following:
1. Use ps and grep to get the PID associated with your userID that started WLS that is using up the CPU.
2. Find the thread id in the WLS process that is using the most CPU via ps -eLo pid,ppid,tid,pcpu,comm | grep.
3. Take several thread dumps of the WebLogic Server process via kill -3.
NOTE: This plan needs to be executed when the issue is actually happening.
troubleshooting process is explained in detail-->
Unexpected High CPU Usage with WebLogic Server (WLS) Support Pattern (Doc ID 779349.1)
Problem Analasys:
In order to properly troubleshoot the high CPU condition Operating System commands are a key to identify the root cause
Please use the following:
1. Use ps and grep to get the PID associated with your userID that started WLS that is using up the CPU.
2. Find the thread id in the WLS process that is using the most CPU via ps -eLo pid,ppid,tid,pcpu,comm | grep
3. Take several thread dumps of the WebLogic Server process via kill -3
NOTE: This plan needs to be executed when the issue is actually happening.
troubleshooting process is explained in detail-->
Unexpected High CPU Usage with WebLogic Server (WLS) Support Pattern (Doc ID 779349.1)
No comments:
Post a Comment