NonStop Server for Java 7.0 Programmer's Reference

$JMETER_HOME/lib/oss, to monitor pre—NSJ7 Java process.1)
2) $JMETER_HOME/lib/oss32, to monitor 32–bit NSJ7 Java process.
3) $JMETER_HOME/lib/oss64, to monitor 64–bit NSJ7 Java process.
b. export JAVA_HOME=/usr/tandem/nssjava/jdk170_h70
c. java -agentlib:jmeter[=options] <application>
4. Start the HPjmeter console from a local installation on your client workstation (HP-UX,
Windows, or Linux). To download HPjmeter consoles for these platforms, visit http://
www.hp.com/go/hpjmeter.
5. Connect to the nodeagent from the HPjmeter console.
NOTE:
• For information on monitoring capabilities and tips, see HPjmeter 4.3 User's Guide available
at www.hp.com/go/hpjmeter.
• The instructions for using the HPjmeter tool on the NonStop systems are provided in
“Addendum to HPjmeter 4.3 user's guide” (page 101).
Collecting profile data for analysis
There are three ways to collect profile data for offline analysis using the HPjmeter console:
1. To enable eprof profiler start the Java application with -Xeprof option.
2. Zero-preparation profiling — start and stop the profile data collection by sending signal to
the running Java application. (This uses the Xeprof profiler, internally, to profile the application
dynamically).
3. The HPROF profiler (start the Java application -agentlib:hprof).
NOTE:
• For information on analyzing profile data, see HPjmeter 4.3 User’s Guide available at
www.hp.com/go/hpjmeter.
• The instructions for using the HPjmeter tool on the NonStop systems are provided in
“Addendum to HPjmeter 4.3 user's guide” (page 101).
-Xeprof
The —Xeprof option generates profile data for HPjmeter. —Xeprof focuses primarily on
performance problems that characterize large server applications. It collects method clock and
CPU times, method call count and call graph, and lock contention statistics.
This option creates profile data file with a file extension .eprof. This file can be opened in the
HPjmeter console and the collected metrics can be viewed.
For more information on this option, see NonStop Server for Java 7.0 Tools Reference.
Zero preparation profiling
Profiling can be started from the command line by sending a signal to the Java process indicating
JVM to start eprof. Engaging zero preparation profiling may have a short term impact on
application performance as the JVM adjusts to the demands of performing dynamic measurements.
To collect profiling data without interrupting your application, perform the following from the
command line:
1. Confirm that no —Xeprof option has been specified on the command-line.
2. Find the process ID of the running Java application.
3. Start the profiling interval — send a signal to the JVM by typing the following command:
kill –USR2 pid
Profiling application performance 87