## Attach to local JVM session |

If the session type in the application settings is set to "Select from all local JVMs", the middle part of the dialog allows you to configure filter settings for the dialog that shows all local JVMs.

When the session is started, a dialog with all locally running JVMs with a minimum version of 1.6 is displayed. Some JVMs are marked with special backgrounds, either as

- Profiled
  if the profiling agent has already been loaded. This may be because the profiling agent was specified on the command line or because you have already attached to that JVM before.
- Offline
  if the application is already profiled in offline mode. To start and stop recording as well as save snapshots in offline profiling mode, use the jpcontroller command line executable.
- Connected
  if the JVM is already connected to by another JProfiler GUI.

You can select any JVM that is not marked as offline or connected and start profiling.

Above the list of JVMs, you find a selector that allows you to modify the filter settings for the displayed JVMs. The list of JVMs supports quick search (just type into it), alternatively you can use the filter field at the bottom to restrict the displayed JVMs.

On Windows, only JVMs that are started by the currently logged in users are shown by default. Often it is required to profile a service that is started by the "Local System" account. In that case, you have to select the toggle button in the upper right corner to add the service JVMs to the list. On Windows Vista and higher, a UAC dialog will be shown to elevate permissions (unless UAC has been disabled). This is required because otherwise those JVMs cannot be discovered and profiled.

Please see the help on attaching to JVMs for more information.