microsoft / microsoft/vscode-java-debug
Debugging a war|exploded war ignores breakpoints
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 591
- Forks
- 429
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 19
Description
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
- deploy war on Tomcat
- start Tomcat in debug mode
- set breakpoints on Java sources
- 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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
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.
Assessment
- Tech stack
- java, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100