[vscode] Extension never activates, throwing error "Header must provide a Content-Length property"

[MarcSerret51]

Describe the bug
As per the title, the extension never activates. The developer tools shows uncaught error: Header must provide a Content-Length property.

To Reproduce
The bug just happened. Tried to downgrade the extension version but doesn't works. Also tried to reinstall VSC but doesn't works.

[BoykoAlex]

@MarcSerret51 which version of vscode? What is the OS (Win? OSX?) What is the path of the project you're opening in VSCode?
The error is JSON RPC issue... content length is different from the actual content length is worrisome :-\ I suspect that one of the JSON messages coming from Boot languafe server to VSCode has a URI with some escaped chars probably or non-printable chars or something like it and hence the length that lsp4j lib computes is different from the actual size of the message... hence the questions above... Would be great to get to the bottom of this

[MarcSerret51]

I'm using VSC 1.7.0 on a Windows 10 NT 64 bits 10.0.19044.
The project path is C:\projects\sources\workspace\EPVT but it also happens with a mini project that I have on the desktop.
It is good to note that I got this bug redhat-developer/vscode-java#2577 on the vscode-java extension that this comment redhat-developer/vscode-java#2577 (comment) solved.
I've been usign both extensions for 3 years without any problem and suddenly both broke.

[martinlippert]

@MarcSerret51 So does adding the workaround, as described here (redhat-developer/vscode-java#2577 (comment)) solves the issue for you for the Spring Tools extension as well? It seems to me like the magic VM argument needs to be added to both extensions (the Java one AND the Spring Tools).

[martinlippert]

If so, we could think about adding this to the default VM args for launching the language server as well, as done here: redhat-developer/vscode-java#2646

[BoykoAlex]

Fixed with aadf4a0

[MunekazuF]

I too have been having problems since around 8/9
SO,I adding -Xlog:disable to java.jdt.ls.vmargs.
In my case -Xlog:jni+resolve=off did not fix it.

Today, Spring Boot Tools was updated to v1.39.0, it stopped working again...

I tried change settings to -Xlog:jni+resolve=off, -Xlog:disable and not set -Xlog properties.
However, the message Header must provide a Content-Length property is still displayed and it does not work.

It works after installing Spring Boot Tools V1.38.0 and setting -Xlog:disable.

Maybe in v1.39.0 vmargs is set at -Xlog:disable -Xlog:jni+resolve=off ?

I'm using VSC 1.71.2 on Windows 10.

[BoykoAlex]

@MunekazuF it is just -Xlog:jni+resolve=off in 1.39. I'll have a look but if you provide your own -Xlog:jni+resolve and -Xlog they should be respected. Do you mind starting jconsole and connecting BootLanguageServer java process and seeing the VM args the process was started with? This would clarify the issue...