Solution : https://service.sap.com/sap/support/notes/743192 (SAP Service marketplace login required)
Summary :
In the SAP environment, high CPU usage on the J2EE Engine server or dispatcher may arise, critically impacting performance. If you encounter this, refer to SAP Note 742395 initially for basic guidance. Detailed diagnostic steps for Linux platforms include utilizing the 'top' command to isolate the most CPU-intensive Java process. Subsequently, a JVM thread dump must be procured; the precise steps differ depending on whether using IBM's JDK (v6.20) or Sun's JDK (v6.30/6.40, 7.00). Established methods enable linking high CPU threads at the OS level with JVM executions, expediting problem resolution. Persistently high CPU usage threads can be further analyzed and correlated using the hexadecimal PID in the thread dump. If complexities persist, pack and escalate the issue, including all relevant diagnostics, to the support team.
Key words :
terms cpu usage utilization 25% 50% 100% loop hang reason, pid user pr ni virt res shr, prio=1 tid=0x080a7048 nid=0x61a7 runnable[4cda9000, %cpu %mem time+ command24929 j2eeadm 9 0 1184 1184 716, process named 'javacore<xxxx>, section 'full thread dump', nid=0x<hexpid>, 24929 ----- register values -----reg_eax, pid directly corresponds, --------------------------------thread dumps produced
Related Notes :
| 1097184 | Analyzing high CPU consumption (IBM JDK on Linux) |
| 742395 | Analyzing High CPU usage by the J2EE Engine |
| 710154 | How to create a thread dump for the J2EE Engine 6.40/7.0 |
| 599539 | J2EE Engine: How to create a full thread dump |
| 171356 | SAP software on Linux: General information |