AS Java Performance issues

[michael_voss2]

Hello everybody!

We're experiencing Performance Problems on our (test) AS Java (7.31). On our Servers, CPU load constantly exceeds 90% and memory usage is high. Looking into the OS, it's basically the Java processes only that are consuming CPU and memory , so we'd like to identify the threads eating CPU and Memory.

In NWDS' Management Console perspective, I see a Problem with so called "red threads". cam anyone Point me to a source of Information about These? I seem not to be able to find any information about these. Also, any help on how to see the current CPU and memory usage of threads inside a JVM would be very helpful.

Thanks in advance

Michael

[michael_voss2 · Accepted solution]

O.k., just to follow up: We found a memory leak in one of our applications. Once we corrected the error, no more red threads would occur. Anyway, these threads could be removed only by restarting the corresponding server node (as would be expected). It would be nice to have a possibility to find more information about those threads in NWDS.

[hemanth2]

Dear Michael,

Hope you are doing good.

The Jstart consuming high CPU time means that server or the bootstrap process consume it. If there are not enough system or application threads  avaliable means that the engine must buffering requests for web application or system processes. Buffering the requests might cause higher CPU time as server processes have to process the requests from the buffers.

Make sure that enough threads are configured.

Please check the note:1016241 - J2EE Engine hangs because of unsufficient system threads

Although it is for 700 servers, you should get a idea on the issue.

SAP KBA: 1625458 will help you check the number of threads on the engine. You can use this when you feel the load on the engine is high / or the server performance is poor and check if there are free threads available.

Once this is done, if you still face the issue, please go through the note 1783031 - Analyzing AS Java

performance with SAP JVM Profiler throughly and do the steps when the CPU usage is high. As the note states, do take a couple of snapshots

and attach the collected *.prf file.

Hope this helps.

_ _ _ _ _ _ _ _ _

Kind Regards,

Hemanth

SAP Active Global Support

_ _ _ _ _ _ _ _ _

[Former Member]

Hallo,

if you click on the red bar for threads you should get an option to view the statistics.

You could also create a thread dump on OS level or via Root-cause-analysis to get more details.

Regards

Thomas