Sap java system working very slow.

[former_member362299]

Hi all,

Average processing time is too high about 200000ms, user complaining that while working portal its working very slow. I checked Heap memory parameter is correct. Oraarch is normal. Please help how to resolve this issue.

Regards

Manjappa

[former_member362299]

can you please step by step process to fix this issue.

Regards

Manjappa

[hemanth2]

Hi Manjappa,

Hope you are doing good. Some simple things that you can check:

1)

Make sure that you are on the latest JVM.A newer JVM will provide you more consistent runtime behaviour, considerably reduce the usage of the JVM's native memory, enhances memory management and improves debugging capabilities.Below will help:

SAP Note No. 1367498 - SAP JVM installation prerequisites

SAP Note No. 1442124 How to download a SAP JVM patch from the SMP

SAP Note No. 1133020 How to import a SAP JVM patch into an AS Java

2)

Please have a look at SAP Note No. 723909.

"

Depending on the use case, load and operational practice the 2GB may not

be sufficient. In this case larger heap size than 2GB can be considered

on 64 bit machines.

"

"

Remark 2: increasing of the heap size or permanent space is harmless on 64 bit systems (given that enough physical memory is available

"

So perhaps you can add another server node or increase the max heap size.
3)

Make sure that enough threads are configured. Please check the note:1016241 - J2EE Engine hangs because of unsufficient system threads. 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.

Navigate to configtool:

Global dispatcher Configuration   > Managers   > ThreadManager

InitialThreadCount = 100

MaxThreadCount = 200

MinThreadCount = 50

Global Server Configuration   > Managers   > ApplicationThreadManager

InitialThreadCount = 100

MaxThreadCount = 350

MinThreadCount = 100

and

Global Server Configuration   > Managers   > ThreadManager

InitialThreadCount = 40

MaxThreadCount = 150

MinThreadCount = 10

4)

And for this particular reason, SAP has developed the Quick Sizer (which is a Web-based tool).

This is available free of cost for customers from:

http://service.sap.com/quicksizer

and

http://service.sap.com/sizing

You will be able to identify whether more hardware/ server nodes etc. are needed and resize the server accordingly. With the Quick Sizer you can translate business requirements into technical requirements. Simply fill in the online questionnaire, an up-to-date survey that is based on business-oriented figures. The results you obtain can help you select an economically balanced system that matches your company's business goals.

Thank you!
____________
Kind Regards,
Hemanth
SAP AGS

[former_member362299]

thanks

[divyanshu_srivastava3]

Hi,

Not a big issue, there are tons of ways to catch the issue.

1st take the thread dumps and analyse it.

Got std_server.out and look for GC. If it on the high side, means the usage of the given heap is high, then you may either have to increase the heap memory or identify the culprit by taking out the heap dump.

Also note down the CPU utilization.

From thread dump, you will get most of the info, I believe in your case, if it's not a GC issue.

Please refer my blog on possible tools.

Regards,

[Former Member]

This message was moderated.