New SAP JVM Profiler 2.0 available!
Want to make sure your Java application is really scalable by consuming only suitable amounts of memory and CPU? You already have problems with long response times in your application or the garbage collection behaviour seems to be strange?
SAP JVM Profiler will help you identify runtime bottlenecks, analyze the memory footprint of your application and find the code causing the problem. Even if you think your application behaves well, it’s often valuable to see what happens “under the hood”.
Profiling your application, let is be on-premise or in the cloud, is easier than ever before in SAP JVM Profiler 2.0: Just select your server JVM in the new VM Explorer, get attached to it by a simple double-cklick and start your favourite profiling trace. Getting the most detailed information about processed garbage collections is now possible with the Garbage Collection Analysis. You also may trigger a Class Statistic or a Heap Dump on demand and analyze the result in statistics or graphically.
Learn about the major 2.0 – features in What is new in SAP JVM Profiler 2.0.
Get more general information about the SAP JVM Profiler here.
Hi Matthias,
As per the documentation :
I downloaded the latest SAP JVM Profiler , imported it into NWDS Archive .
Then NWDS restarted automatically, I then opened the VM Explorer perscpective.
I have started the daemon jvmmond on several remote hosts (default port 1099 being used)
VM Explorer is capable to communicate with the remote hosts (state is green = Valid host)
The Activate column has been checked.
The VM hosted on remote Unix hosts are displayed (after restarrting again NWDS
While the VM hosted on remote Windows remain desperatly empty
There are several sap system running on the remorte windows hosts, port 1099 is used by the daemon jvmmond ... so ... I do not understand
Thanks
Hi Raoul,
what kind of NetWeaver System is running on the remote windows host? Are you sure that there is at least one SAP JVM instance running? Older releases (7.0x and older) may also run on JVMs from different vendors (Oracle/Sun in case of windows). You should also start the jvmmond with the SID adm user. This is necessary to attach the SAP JVM later on.
To exclude some basic problems, please start a standalone SAP JVM on the windows host (release not older than 1 year; you find a current release on https://tools.hana.ondemand.com/#cloudhttp://wiki.scn.sap.com/wiki/display/ASJAVA/Download+the+SAP+JVM+Profiler+2.0+plug-in).
I hope this will solve the problems. If not, please feel free to contact again.
Best regards,
Matthias