Closed bpeCRtMU closed 1 month ago
Do you have XDG_RUNTIME_DIR
defined ? Looks like it might be too long (>70 chars) on MacOS.
I'm getting the same error message.
How can we check for this var? I have not changed my environment in the last few days (although VS Code was updated).
Until this is fixed, try setting "java.transport" : "stdio"
in your vscode settings. See https://github.com/redhat-developer/vscode-java/issues/3634#issuecomment-2096242414 for more details
Fred brought up a good point (in discussions), which is that we should be able to restart the language server with stdio
if it fails the first time with pipe
. The failure happens at https://github.com/redhat-developer/vscode-java/blob/2f5094fb858235120f55952cfb8f6ec987a1a4ac/src/TracingLanguageClient.ts#L32-L36, which is actually well before the initializationFailedHandler
gets registered. This complicates relaunching.
Maybe we can improve this.
Upon closing and reopening VS Code the Java Language Server fails to start due to the following error:
Quitting and restarting VS Code does not solve this issue. However, restarting the computer and reopening VS Code works. Meaning the extension works again until you close the window.
Environment
MacOS Sonoma 14.4.1
orDarwin arm64 23.4.0
jdk-21
, project jdk: 171.89.1
Steps To Reproduce
Logs
The Java Extension did not produce a log file as it could not start.
VS Code: