Page tree
Skip to end of metadata
Go to start of metadata


SAP Note 1783031 explains how SAP JVM Profiler can be used to analyze the AS Java performance. This page illustrates the steps for SAP ME system in particular.


1. Launch jvmprof

Launch jvmprof from the path of SAP JVM which is used by AS Java (\usr\sap\SID\J##\exe\sapjvm_#\bin):

2. Enter the systemnumber

Enter the systemnumber.

3. Display VMS

display vms

4. Start profiling

Start the profiling process by executing the following sequence of commands in the prompt. (where "VmId" has to be replaced with the server process experiencing bad performance and "" with some valid path on the file system and profiler_output.prf with the name of the output file in .prf extension):

  • start profiling "VmId" dest=""\profiler_output.prf

    after this command the output file in .prf extension is generated in the specified directory, which can be checked on the file system 


Then execute:

  • start performance hotspot trace "VmId" ignoreSleepingThreads=false

5. Execute the scenario in SAP ME

Execute the scenario in SAP ME that is causing performance problems. If possible, direct the requests to the chosen server process intentionally.

6. Stop profiling

Stop the profiling process by executing:

  • stop performance hotspot trace "VmId"
  • stop profiling "VmId"

7. Check the output file

You can verify whether some dump was captured by checking the size of the output file.

8. Send to SAP

Provide the output file to SAP Support to analyze it

Related Documents

(TSG) SAP JVM Profiler
Java Profiling

Related Notes

SAP Note 1783031 - Analyzing AS Java performance with SAP JVM Profiler

SAP Note 2176018 - How to access JVMMond behind a firewall to monitor JVM performance

SAP Note 2151862 - How to analyse connection issues to the message server

SAP Note 2677090 - Enable Debugging Profiling Port for JVM Profiling using jvmmon command line interface


  • No labels