The Language Support for Java server crashed 5 times in the last 3 minutes. The server will not be restarted.

[scotshall]

Receiving the following error when opening a Maven project folder:

The Language Support for Java server crashed 5 times in the last 3 minutes. The server will not be restarted.

Environment

• Operating System: Windows 10

• JDK version: both java version "1.8.0_141" AND openjdk version "11.0.1" 2018-10-16

• Visual Studio Code version: Version: 1.29.1 (user setup)
  Commit: bc24f98b5f70467bc689abf41cc5550ca637088e
  Date: 2018-11-15T19:13:36.375Z
  Electron: 2.0.12
  Chrome: 61.0.3163.100
  Node.js: 8.9.3
  V8: 6.1.534.41
  Architecture: x64

• Java extension version: 0.35.0 (November 30th, 2018)

Steps To Reproduce

1. Install the Language Support for Java(TM) by Red Hat extension (no other extensions are active)
2. Create a new Maven project using the quickstart archetype
3. Open the folder with the new Maven project
4. See the error

I am unable to attach the Java Language Server log file. I followed the steps here, but when I run the the Java: Open Java Language Server log file command nothing happens.

Current Result

Expected Result

Additional Informations

[scotshall]

I've also set up Code to run on the Windows Ubuntu app an am getting the same error.

[scotshall]

I tried cleaning the workspace directory as per the instructions found here, but I am getting the same error.

[fbricon]

do you see any org.eclipse.equinox.launcher*.jar processes when running jps? If you find any try to kill them.
Also, try to run with the latest Java 1.8 version.

[scotshall]

There are no jps processes running other than jps itself.

I've updated to the latest version of JDK 8 (java version "1.8.0_191"), but I'm getting the same error.

I was able to manually start the Eclipse JDT Language Server following the instructions here, so I know it will run (although I still get the same error in code even if the server is manually started).

[fbricon]

any antivirus running?

[scotshall]

It's a corporate PC, so, unfortunately, yes. However, I'm not see anything in it's logs about it blocking any java or code processes. Also, I was able to (temporarily) borrow a PC and I'm not getting any errors there when I load a Java project in code. (I suppose they could be using different antivirus definitions, but they're both corporate so they should be in sync.)

Those in change of such things have decided to use Carbon Black for AV protection. Do you know of any specific issues with Carbon Black?

[fbricon]

I'd be curious if disabling the AV (probably wanna be offline for that) makes any difference. And I know nothing about AVs, except they can wreak havoc sometimes.

In your settings.json, try to :

• set "java.trace.server":"verbose"
• add -Dlog.level=ALL to the default "java.jdt.ls.vmargs" value

after restarting, get the Java server logs from VS Code's Output view

[scotshall]

Thank you for giving me the "java.jdt.ls.vmargs" setting, I was able to figure out what was going wrong.

I had installed the Lombok Annotations Support for VS Code extension awhile back and decided to remove it. However, the extension added some parameters to the java.jdt.ls.vmargs setting:
"-noverify -Xmx1G -XX:+UseG1GC -XX:+UseStringDeduplication -javaagent:\"C:\\Users\\SHall\\.vscode\\extensions\\gabrielbb.vscode-lombok-0.9.7/server/lombok.jar\" -Xbootclasspath/a:\"C:\\Users\\SHall\\.vscode\\extensions\\gabrielbb.vscode-lombok-0.9.7/server/lombok.jar\""

When I removed the extension, the settings were still present but the Language Server was unable to the load the manifest from the lombok.jar file (because it was deleted). This caused the Language Server to fail to start.

After adding the -Dlog.level=ALL parameter to the java.jdt.ls.vmargs setting, I was finally able to see the error in the output view. I've put the java.jdt.ls.vmargs setting back to its default value and everything is working properly again.

Thank you for your help! You can close this issue.

[fbricon]

Ok, good to know, that info might be helpful to others

[Ivaylo2017]

I had this problem too and it had occurred after i changed my _JAVA_OPTIONS env variable on Windows. I noticed that some plugins import their own setting in VS Code Settings -> settings.json
To fix the error - You have to update them with -Xmx to be larger than the system -Xms value.
I made them identical in both locations and the error is gone. Hope this helps!