TransportTimeoutException when debugging Java project on Windows 11 and integratedTerminal

[erikson84]

I'm using nvim-dap and nvim-dap-ui, together with nvim-jdtls, to debug a Spring backend application using Neovim v.10.1 and LazyVim. It used to work just fine, with the Spring output directed to the console window of nvim-dap-ui.

Recently, and I wasn't able to trace that exactly changed, every Java application I tried to debug in my setup incurred in a TransportTimeoutException (with the additional information "Failed to launch debuggee in terminal").

I checked the docs and I found in MS java-debug-adapter configuration that I should change my "console" option to "internalConsole" in the launch.json file. With this option, I'm able to debug again, but all output goes to the DAP console without escaping ANSI characters.

I'm hoping for some suggestions to better diagnose what is happening and why the integratedTerminal option is causing the timeout error. Thanks!

[Edit] Eventually, the following error log appear in the dap-ui integrated terminal windows:

ERROR: transport error 202: recv failed during handshake: Connection reset by peer
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [t:\workspace\open\src\jdk.jdwp
.agent\share\native\libjdwp\debugInit.c:734]

[Process exited 2]

[erikson84]

By chance, I found this discussion with an unrelated problem, but I decided to try the solution and added the "shortenCommandLine": "argfile" to my launch.json, and it worked! I believe the long classpath (it's a big company project!) might be the reason the integrated terminal failed to launch.