Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Debugging a war|exploded war ignores breakpoints

Open
#1,405 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, vscode
Domain
devtools

Research direction

Reproduce the issue with the listed JDK, VS Code, Java debugger, Community Server Connectors, and Tomcat versions using both a WAR and an exploded WAR. Start with the deployment and breakpoint behavior described in the reproduction steps; done means navigation through the web app pauses at Java source breakpoints and highlights the reached line.

Written by the indexing model from the issue text.

Description

ai-triaged question

After the deploy on Tomcat of a war or an exploded war and having set breakpoints, the execution does not stops successfully at the breakpoints.

Environment
  • Operating System: Win10 Pro - Build No : 19045.3570 version : 22H2
  • JDK version: JDK 1.8.0_371
  • Visual Studio Code version: 1.84.0 User Setup
  • Java extension version: Extension Pack for Java v0.25.15
  • Java Debugger extension version: Debugger for Java v0.55.0
  • Community Server Connectors v0.26.13
  • Application Server: Tomcat-7.0.109
Steps To Reproduce
  1. deploy war on Tomcat
  2. start Tomcat in debug mode
  3. set breakpoints on Java sources
  4. navigate the webapp in order to hit breakpoints
Current Result

The breakpoints are ignored, as if the breakpoints are not set

Expected Result

The execution should stop at breakpoints, highlighting the source code row reached

Dominant language
TypeScript
Stars
591
Forks
429
Avg merge
1d 9h
Merged PRs (30d)
19

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-java-debug

All issues in microsoft/vscode-java-debug

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.