HPjmeter 4.2 User's Guide

noalloc
Reduces dormant overhead by skipping bytecode instrumentation that applies to object
allocation metrics: Allocated Object Statistics by Class and Allocating Method Statistics. The
noalloc option makes those metrics unavailable.
Example usage: -agentlib:jmeter=noalloc
nohotspots
Reduces dormant overhead by skipping the bytecode instrumentation that supports Java
Method HotSpots. Any console connecting to an application initially started with this agent
flag does not enable Java Method HotSpots, and this metric is not listed in the Session
Preferences dialog.
Example usage: -agentlib:jmeter=nohotspots
noexception
Reduces dormant overhead by skipping bytecode instrumentation that applies to the Thrown
Exception metrics. Any console connecting to an application initially started with this attribute
does not enable Thrown Exception metrics, and these metrics are not listed in the Session
Preferences dialog.
Example usage: -agentlib:jmeter=noexception
nomemleak
Reduces dormant overhead by skipping bytecode instrumentation that applies to memory
leak location events. When you specify this option, the memory leak location alert is
unavailable in the console for the lifetime of this application.
Example usage: -agentlib:jmeter=nomemleak
noarrayleak
Reduces dormant overhead by skipping bytecode instrumentation that applies to array leak
location events. When you specify this option, the array leak location alert is unavailable in
the console for the lifetime of this application.
Example usage: -agentlib:jmeter=noarrayleak
owner_private
Specifies that the JVM is visible only to the node agents run with the same effective user ID;
that is, run by the same user as the one who runs the JVM. This limitation does not apply to
node agents run as root (the installation default).
• You can specify only one of the options owner_private, group_private, or public.
• Example usage: -agentlib:jmeter=owner_private
public
Specifies that the JVM is visible to all node agents run on the same host as the JVM.
• You can specify only one of the options owner_private, group_private, or public.
• Example usage: -agentlib:jmeter=public
verbose[:file=filename]
Prints information about the bytecode instrumentation rules in effect, such as include or
exclude settings, and about the individual instrumentation decisions made for all loaded
classes. By default, the information is printed on stdout. You can override this by specifying
a file name, for example verbose:file=bci.txt.
Example usage: -agentlib:jmeter=verbose
version
Displays the JVM agent version and quits immediately without running any Java applications
at all. You cannot use this option with any other options.
Example usage: -agentlib:jmeter=version
20 Completing Installation of HPjmeter