To find the "Root Cause" for OPP (java) processes consuming High CPU. Most of the time it is due to un-optimized "Template Code" that causes slowness. This document helps to identify the "Template code" that could be the potential cause. It could be either Standard Template Code (provided by Oracle) or Custom (designed by in-house team).
Issue:
Below Steps to Identify/Resolve the OPP (java) process issue.
1. Identify <PID> of OPP that is spinning. Use top (or) prstat
2. Generate the java thread dump.
2.1 $kill -3
3. Get “thread ID” which consumes High CPU. Use this command.
3.1 $ ps -eLo pid,ppid,tid,pcpu,comm | grep <PID>
4. Convert the “thread ID” to Hexadecimal which helps to identify the “Template code” (potential cause).
5. Resolution - Optimizing the Template code.
(Ref: Doc ID 2028617.1)
Issue:
Below Steps to Identify/Resolve the OPP (java) process issue.
1. Identify <PID> of OPP that is spinning. Use top (or) prstat
2. Generate the java thread dump.
2.1 $kill -3
3. Get “thread ID” which consumes High CPU. Use this command.
3.1 $ ps -eLo pid,ppid,tid,pcpu,comm | grep <PID>
4. Convert the “thread ID” to Hexadecimal which helps to identify the “Template code” (potential cause).
5. Resolution - Optimizing the Template code.
(Ref: Doc ID 2028617.1)
No comments:
Post a Comment