YourKit Manually Configure Target JVM for Remote Profiling: Difference between revisions
Jump to navigation
Jump to search
| Line 22: | Line 22: | ||
java -agentpath:<''profiler-agent-path''>=help | java -agentpath:<''profiler-agent-path''>=help | ||
Once the target VM has been instrumented and it is listening on a profiler-dedicated port, the profiler UI can connect to it over a variety of means (directly, by | Once the target VM has been instrumented and it is listening on a profiler-dedicated port, the profiler UI can connect to it over a variety of means (directly, by [[YourKit_Operations#Connect_to_a_Remote_Instrumented_JVM_via_SSH|initiating a SSH connection from the profiler UI]], by using a SSH tunnel, etc.) | ||
=Options= | =Options= | ||
Revision as of 00:50, 9 June 2018
External
Internal
Overview
Start the JVM with the following configuration:
java ... -agentpath:<profiler-agent-path>[=options] ...
Linux example
java ... -agentpath:<profiler-directory>/bin/linux-x86-64/libyjpagent.so
To check that Java can load the profiler agent, run:
java -agentpath:<profiler-agent-path>=help
Once the target VM has been instrumented and it is listening on a profiler-dedicated port, the profiler UI can connect to it over a variety of means (directly, by initiating a SSH connection from the profiler UI, by using a SSH tunnel, etc.)
Options
Example:
java ... -agentpath:<profiler-agent-path>=port=8080,alloceach=10,allocsizelimit=4096 ...
Startup options:
port
The port the profiler agent listens on for communication with the profiler UI. By default, the port is chosen automatically, starting with 10001. The first port free in the 10001..10010 range is used.