After recent update, breakpoints fail to bind when attaching to JVM in WSL2 (Windows host) — rollback fixes

[clertonbruno]

Environment

• Host OS: Windows 11, IDE: Cursor/VS Code (Windows) with repo via WSL2
• Guest OS: WSL2 Ubuntu 22.04
• Java: OpenJDK 1.8.0_432 (Java 8)
• Extensions: Debugger for Java (latest), Language Support for Java™ by Red Hat 1.47.0
• Project: Spring Boot API (Gradle), attach debug on port 5005

Expected behavior
Attach to JDWP and stop at breakpoints.

Actual behavior
Attach to 127.0.0.1:5005 connects but no IDE breakpoint is hit; HTTP requests hang. Attaching with jdb works fine. Rolling back Language Support for Java and Debugger for Java to earlier versions (e.g., 1.46.0 and 0.58.2) resolves the problem.

Steps to reproduce

1. Build and run jar with JDWP:

   ./gradlew clean assemble -x test
   java -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=5005 \
        -Dspring.profiles.active=local -Duser.timezone=UTC \
        -jar build/libs/*.jar

2. In Cursor/VS Code (Windows), use attach configuration to 127.0.0.1:5005.
3. Set breakpoints in Spring @RestController method.
4. Call the endpoint from a client.

Notes
Seems specific to Windows/WSL2 remote debugging; not reproducible on native Windows. Verified JDWP and line number tables are present. Rolling back both extensions resolves.
Rolling back both extensions resolves.

[fbricon]

vscode-java doesn't include any debugging facilities OOTB, please open a ticket in https://github.com/microsoft/java-debug/issues

[clertonbruno]

Thanks for the clarification and quick response, @fbricon! I'll follow your suggestion and file the bug in the microsoft/java-debug repository. Appreciate your help.