Component : Java Application Server - Please use sub-components - IBM AIXBC-OP-AS4 IBM AS/400BC-OP-FTS-SOL Fujitsu SolarisBC-O

Solution : https://service.sap.com/sap/support/notes/743191 (SAP Service marketplace login required)

Summary :
This SAP note addresses high CPU usage issues in a J2EE Engine node, potentially linked to runaway threads in the java or jlaunch process. Users observing high CPU must use the `ps -mp -o THREAD` to identify offending threads by their high CPU time and thread state. Furthermore, thread dumps are required (via methodologies detailed in notes 599539, 710154 depending on JVM version) to analyze thread activities at the Java level. The final step involves mapping OS-level thread IDs to JVM thread dumps, which varies between Hybrid and Classic JVMs. This process is necessary for isolating and resolving performance issues.

Key words :
pthread addr = 0x00000001130b0a2c         size         = 0x3e8         vp addr      = 0x00000001130b3d48        size        = 0x2e0        thread errno = 0         start pc    = 0x8001000a005da98        joinable    =, k-tid mode held scope function$t1    wait      0xf100008790030a40 blocked  3186699, thread    user    pid    ppid      tid st  cp pri sc    wchan, k-tid mode held scope function $t10    run                          running  3641457, base        = 0x112fb0000         size        = 0x100000         limit        = 0x1130b0a2c        sp           = 0x1130aecb8, terms cpu usage utilization 25% 50% 100% loop hang reason, sys _p_nsleep$t3    wait      0xf10000879001f240 blocked  2040023, sys _event_wait$t4    wait      0xf10000879003ba40 blocked  3907723, sys _event_wait$t5    wait      0xf100008790009340 blocked   602357, sys _event_wait$t6    wait      0xf100008790020640 blocked  2121827

Related Notes :

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