Run/Debug Configuration: Remote Debug
Use this dialog to create a debug configuration to be used for remote debugging processes such as applications, servlets, plugin applets, and so on. Remote debugging enables you to connect to a running JVM.
The dialog consists of the following tabs:
Configuration tab
| Item | Description |
|---|---|
| Command line arguments for running remote JVM | These read-only fields show the command-line arguments to be used for running a remote JVM. MPS suggests two arguments, depending on the JDK version used. |
| Transport: Socket | If the Socket transport is selected, specify host where the remote process is running and to which the debugger will connect. Specify also the port on remote host to which the debugger should connect. |
| Transport: Shared Memory | Having selected Shared memory transport, specify the shared memory address in the text field. This kind of transport is available for Windows only. |
| Debugger mode: Attach | Select this radio button is you want the debugger to connect to a running remote JVM. |
| Debugger mode: Listen | Select this radio button is you want the debugger to run as a server for remote JVM's which will connect to it to perform debugging. In this case the Host field will be disabled (if the Socket transport is selected). The Port value is considered as a port at which the debugger-"server" will listen to connections from the debugger-"clients". |
Common
When you edit a run configuration (but not a run configuration template), you can specify the following options:
Item | Description |
|---|---|
Name | Specify a name for the run/debug configuration to quickly identify it when editing or running the configuration, for example, from the Run popup Alt+Shift+F10. |
Allow parallel run | Select to allow running multiple instances of this run configuration in parallel. By default, it is disabled, and when you start this configuration while another instance is still running, MPS suggests to stop the running instance and start another one. This is helpful when a run/debug configuration consumes a lot of resources and there is no good reason to run multiple instances. |
Store as project file | Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project. By default, it is disabled, and MPS stores run configuration settings in .idea/workspace.xml. |
Toolbar
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.
| Item | Shortcut | Description |
|---|---|---|
 | Alt+Insert | Create a run/debug configuration. |
 | Alt+Delete | Delete the selected run/debug configuration. Note that you cannot delete default configurations. |
 | Ctrl+D | Create a copy of the selected run/debug configuration. Note that you create copies of default configurations. |
 | The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent. | |
 | View and edit the template (that is, the default run/debug configuration settings). The templates are displayed under the Templates node and used for newly created configurations. | |
 /  | Alt+Up/ Alt+Down | Move the selected run/debug configuration up and down in the list. The order of configurations in the list defines the order, in which the configurations appear when you choose a run/debug configuration. Default templates of run/debug configurations are always sorted alphabetically. |
 | Move into new folder / Create new folder. You can group run/debug configurations by placing them into folders. To create a folder, select the configurations within a category, click Then, to move a configuration into a folder, between the folders or out of a folder, use drag or To remove grouping, select a folder and click | |
 | Click this button to sort configurations in the alphabetical order. |
, and specify the folder name. If only a category is in focus, an empty folder is created.Before Launch
In this area, you can specify tasks to be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
| Item | Shortcut | Description |
|---|---|---|
| Alt+Insert | Click this icon to add one of the following available tasks:
|
| Alt+Delete | Click this icon to remove the selected task from the list. |
 | Enter | Click this icon to edit the selected task. Make the necessary changes in the dialog that opens. |
| / | Alt+Up/ Alt+Down | Click these icons to move the selected task one line up or down in the list. The tasks are performed in the order that they appear in the list. |
| Show this page | Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration. | |
| Activate tool window | By default this checkbox is selected and the Run or the Debug tool window opens when you start the run/debug configuration. Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5. |