Skip Headers
Previous
Previous
 
Next
Next

Starting the DTrace Recorder

The DTrace Recorder server will execute a dtrace script on the same machine as the profiled application, the dtrace script creates a recording that can be visualized in Mission Control.

If Java Mission Control runs on another host than the profiled application, the DTrace Recorder server will run as a separate java program.

If Java Mission Control runs on the same host, the DTrace Recorder server runs as part of Mission Control application itself.

The DTrace Recorder server needs to run with dtrace privileges and with dtrace in PATH. For more information, see "Setting Up DTrace Privileges".

The ps in your PATH should not be the BSD version in /usr/ucb.

The DTrace Recorder server needs to have the tools.jar on the bootclasspath.

If you are running the profiled application on the same host as Java Mission Control, the DTrace Recorder server is run as part of Java Mission Control itself. Start it as you normally would, and locate the JVM you want to profile in the JVM Browser.