Starting Remote Sessions

  In most cases, the integration of JProfiler with an application server is handled by the application server integration wizards. If no GUI is available on the remote machine you can use the jpintegrate executable in the bin directory for a console integration wizard.
  If you want to quickly profile a JVM of version 1.6 or higher on a remote machine, extract a JProfiler archive from the download page on the remote machine. You do not have to enter a license key there. Run the bin/jpenable command line application on the remote machine. You will be able to select a JVM and load the profiling agent into it so that is listens on a specific profiling port.

In your local JProfiler GUI, create an "Attach to remote JVM" session and enter the host name and the same profiling port that you specified in jpenable on the remote machine.

  You can always profile a JVM by adding a VM parameter to the Java start command that loads the JProfiler agent. In the JProfiler GUI, you then create a session of type "Attach to remote JVM" and connect to the profiled JVM.

See the help page on manually Adding The Profiling Agent for detailed instructions.

  Please note that the profiling interface JVMTI only runs reliably with the standard garbage collector. If you have VM parameters on your command line that change the garbage collector type such as
  • -Xincgc
  • -XX:+UseParallelGC
  • -XX:+UseConcMarkSweepGC
  • -XX:+UseParNewGC
please make sure to remove them. It might be a good idea to remove all -XX options if you have problems with profiling.
  If you start your application from an ant build file, you can use the ant task to easily profile your application.