You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Debug session never starts: TransportTimeoutException in launch and attach modes (TCP connection established) #1733
Language Support for Java (redhat.java): 1.58.0 (also seen on pre-release 1.59.2026111308)
Debugger for Java: [version]
Language server runtime: bundled JRE 25.0.4.1 (also 25.0.5 on the pre-release)
Debuggee JDKs: Temurin 8u482 and 17.0.20 (same result with both)
Debugger for Java: latest available as of 2026-11-18 (auto-updated; exact version not captured before uninstalling)
Problem
Debugging stopped working after an extension update; it previously worked on the same project and machine.
Run works fine. Debug never hits breakpoints and fails with:
Launch: "Failed to launch debuggee in terminal. Reason: com.sun.jdi.connect.TransportTimeoutException"
Attach: "Failed to attach to 127.0.0.1:5005 (attach timeout 30000, handshake timeout 0)"
What I verified
The debuggee starts with -agentlib:jdwp=transport=dt_socket,server=n,suspend=y,address=localhost:<port> and hangs before main.
During the hang, netstat shows the TCP connection is ESTABLISHED between the language server process (listening on 0.0.0.0/[::]) and the debuggee, so the socket connects but the JDWP handshake or VM init never completes.
Same result with console: internalConsole (launched via -Xrunjdwp).
Same result in a clean VS Code profile with freshly installed extensions.
Outside VS Code, jdb from JDK 17 (-connect com.sun.jdi.SocketListen) accepts the same debuggee connection immediately ("VM Started").
IntelliJ IDEA debugs the same project on the same machine without issues.
java.jdt.ls.java.home pointing to JDK 21 was not applied (language server still started on bundled JRE 25), so I couldn't test with a different runtime.
Activity