Setup remote debug tomcat

Ant patterns that define the range of files to be displayed. Aliases to substitute for full paths or patterns. These aliases are also displayed in the headers of the tabs where the corresponding log files are shown. If a log entry pattern defines more than one file, the tab header shows the name of the file instead of the log entry alias.

Select this checkbox to save the console output to the specified location. Type the path manually, or click the browse button and point to the desired location in the dialog that opens. Select this checkbox to activate the output console and bring it forward if an associated process writes to Standard. Click this button to open the Edit Log Files Aliases dialog where you can select a new log entry and specify an alias for it.

Click this button to edit the properties of the selected log file entry in the Edit Log Files Aliases dialog. Use this tab to configure code coverage monitoring options. Select this option to collect accurate branch coverage. Use or to add classes or packages to the list. To remove the classes or packages from the list, select the corresponding list items and click.

Clear this checkbox to change the parameters passed to the script or to specify a different script:. To specify the script, click and select the desired script in the dialog that opens.

Use spaces to separate individual parameters and options, for example, -client -ea -Xmxm. If a parameter or an option includes spaces, enclose the spaces or the argument that contains the spaces in double quotes, for example, some" "arg or "some arg".

If a parameter or an option includes double quotes e. To pass specific variables to the server environment, select this checkbox and specify the variables:. To add a variable, click and specify the variable name and value in the Name and Value fields respectively.

To remove a variable from the list, select the variable and click. Click this button to edit the debugger options on the Debugger page of the Settings dialog. This tab shows command-line options for starting the server JVM in the run and debug modes.

Use to switch between the settings for the run and debug modes. The command-line options for starting the server JVM. These are shown just for copying elsewhere. When you edit a run configuration but not a run configuration template , you can specify the following options:. By default, it is disabled, and when you start this configuration while another instance is still running, IntelliJ IDEA suggests to stop the running instance and start another one.

Save the file with the run configuration settings to share it with other team members. The default location is. However, if you do not want to share the. 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. To create a folder, select the configurations within a category, click , and specify the folder name. If only a category is in focus, an empty folder is created. Then, to move a configuration into a folder, between the folders or out of a folder, use drag or and buttons. To remove grouping, select a folder and click. The tasks are performed in the order they appear in the list. Run External tool : select to run an external application.

In the dialog that opens, select one or multiple applications you want to run. For more information, see External tools and External Tools. In the dialog that opens, select the configuration to be run. Build : select to compile the specified module. The Build Module command will be executed. Build Project : select to compile the entire project. The Build Project command will be executed.

Build Artifacts : select this option to build an artifact or artifacts. In the dialog that opens, select the artifact or artifacts that should be built.

Launch Web Browser : select this option to have a browser started. In the dialog that opens, select the type of the browser and provide the start URL. Also, specify if you want the browser be launched with JavaScript debugger. Run Ant target : select this option to run an Ant target. In the dialog that opens, select the target to be run. Run Grunt task : select this option to run a Grunt task.

In the Grunt task dialog that opens, specify the Gruntfile. Specify the location of the Node. Run gulp task : select this option to run a Gulp task. In the Gulp task dialog that opens, specify the Gulpfile. Run Maven Goal : select this option to run a Maven goal.

In the dialog that opens, select the goal to be run. Run npm script : select this option to execute an npm script. Compile TypeScript : select to run the built-in TypeScript compiler and thus make sure that all the changes you made to your TypeScript code are reflected in the generated JavaScript files. In the TypeScript Compile Settings dialog that opens, select or clear the Check errors checkbox to configure the behaviour of the compiler in case any errors are detected: If the Check errors checkbox is selected, the compiler will show all the errors and the run configuration will not start.

If the Check errors checkbox is cleared, the compiler will show all the detected errors but the run configuration still will be launched.

In the dialog that opens, specify where your CoffeeScript source files are located. Run Rake task : add a Rake task to be executed prior to running or debugging. To choose a Rake task, click the browse button , and select the desired task from the list of available tasks. Note that code completion is available here. Run JRuby compiler : choose this option to execute JRuby compiler with the specified target path, compiler process heap size, and command line parameters if any.

Click these icons to move the selected task one line up or down in the list. Read the download instructions carefully, as they package Eclipse with everything you need, the prerequisite software and WTP, or just WTP. Eclipse and WTP have already been installed on Institute lab computers.

The explanation which follows might help you install and configure WTP similarly in another environment. Add your servlet code and test it using the local environment Deploy your tested code to a remote tomcat server running from your account.

Create a Web Archive. Therefore, you need to use the section "WAR file to deploy" and click on the Browse That file will be uploaded when you click on the Deploy button.

If you don't see that, read or re-read Using the Tomcat Development Service. If all else fails, contact an Institute lab staff member. This may be important because every line of code in the Java source usually corresponds to multiple bytecode instructions. Finally, thanks to the attached sources, you can see the contents of the source code line on which the break occurred. To check out all methods in a class, you can use the corresponding command.

The classes command lets you explore the available loaded classes, but the number of them in a Spring-based web application would be pretty large and not very easy to navigate. You can easily see all local variables and method arguments in the current scope with the locals command:.

The print command is pretty useful, as it is the evaluation tool that has been around long before the jshell utility appeared in Java 9. The print command can be used to output anything that is accessible in the current scope. You can also use the step up command to run the code to the end of the current method, exit it and stop at the next line of the calling method:.

After that, the page in the browser will be loaded successfully, but the message will be different. The jdb utility is definitely very powerful, but if you have the option, debugging in your favorite IDE is clearly easier. The debug configuration is pretty easy to set up in any Java IDE. The default configuration is mostly good, you just have to provide a meaningful name and change the port to , as in the example:.

Now start the created debug configuration and put a breakpoint on a line of code. You should see a tick inside the red bubble, which means that the debugger is attached and ready to intercept:. Now open the page in the web browser, and the debugger should stop at the breakpoint. The source code for the article is available over on GitHub. Click here to read more about the acquisition.

Try Our Free Code Profiler. Try Our Code Profiler. By Role. By Technology. By Language. Documentation Support Ideas Portal Menu. Start Free Trial. About the Author Latest Posts.