-
Notifications
You must be signed in to change notification settings - Fork 414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keep getting "Couldn't start client Language Support for Java" when opening a Java file in vscode. #1813
Comments
I believe that the error is from this part of
|
The exception points out the failure is from invalid javadoc URL. Could you comment out the javadoc config for JDK 15 in your user setting? @snjeza What's the correct format to configure the javadoc in "java.configuration.runtimes" setting? |
Commenting it out seems to fix it for now but I do want to figure out how to fix that javadoc URL. |
I think I managed to get it working by replacing |
Good to know you figured it out. Yes, there is room for us to improve this. Considering the peer keys in this setting support a local path, but not for javadoc is a bit confusing. Also the invalid URL should not break the starting of Java tooling itself. |
You can try https://docs.oracle.com/en/java/javase/15/docs/api/ |
Thanks |
Whenever I open a .java file in a workspace, I get the errors "Couldn't start client Language Support for Java" and "Couldn't start client Language Support for Java (Syntax Server)". I was previously able to use the Java extension in this same workspace.
Environment
Steps To Reproduce
[Please attach a sample project reproducing the error]
Monday Class.zip
Please attach logs
Logs.zip
Note: In the logs, I replaced some of the parts of the paths to my project location and also my username with ******* for privacy.
Current Result
Errors "Couldn't start client Language Support for Java" and "Couldn't start client Language Support for Java (Syntax Server)".
Expected Result
No error when loading vscode Java extension.
Additional Informations
The text was updated successfully, but these errors were encountered: