Language Support for Java(TM) by Red Hat - Couldn't start client Language Support for Java

atang0404 commented 7 years ago

Hi guys:

I just recently installed the Language Support for Java extension however, I can't seem to get it working. Whenever I open a Java file I get a message stating the it "Couldn't start client Language Support for Java".

I get an error output that reads:

[Error - 11:54:37 PM] Starting client failed 13

I've already checked to see if JAVA_HOME is mapped under Environment Variables and it has. Any help would be appreciated. Thanks! Alexander Tang

atang0404 commented 7 years ago

Also....

fbricon commented 7 years ago

Can you try with java home not containing spaces?

linonetwo commented 7 years ago

I tried C:\Progra~1\Java\jdk1.8.0_91 but it still warns The JAVA_HOME environment variable could not be detected, or it doesn't point to a JDK.

linonetwo commented 7 years ago

I have set

JAVA_HOME C:\Java\jre1.8.0_102

JDK_HOME C:\Java\jdk1.8.0_102

still not working

fbricon commented 7 years ago

JAVA_HOME pointing to a JRE will certainly not work. It has to be a JDK. JDK_HOME is not supported. I'll have to try it on Windows to see what's happening.

linonetwo commented 7 years ago

It's OK if I set JAVA_HOME to C:\Java\jdk1.8.0_102, but there is a downside thumbnail.

↙ Like this one.

ghost commented 7 years ago

I'm no expert nor am I the best when it comes to coding but I believe the downside thumbnail indicates no maven hierarchy. I set my JAVA_HOME to the JDK and all my errors disappeared but now I'm stuck with the downside thumbnail. @linonetwo Other tickets have stressed the extension doesn't support Java files without the hierarchy.

If I use Eclipse to initially compile my Java files will that work? @fbricon

vabatta commented 7 years ago

I also have the same problem, after setting the JAVA_HOME I got the thumb down (which implies that some features won't work right?). Do actually need some other sort of file to get it working (like a build.xml or some other IDE-Java file related, think of maven) in the project folder?

fbricon commented 7 years ago

@vabatta you need:

a JAVA_HOME env variable pointing to a JDK (not JRE) home directory
to open a folder containing a Maven pom.xml ideally. Eclipse .project/.classpath settings are somehow supported, to a lesser degree. So for instance, if you have a gradle project, you can try to generate the eclipse settings before opening the project.

In case it doesn't work, click on the thumb down icon to access some logs

maxtar commented 7 years ago

I have the same. But is it extension can open only maven project? What about just java files?

fbricon commented 7 years ago

@maxtar we're working on it (#27). Problem is standalone java files provide no context, no classpath. Displaying tons of compilation errors would be detrimental in that case. We're looking into providing a minimal content assist for basic Java apis in that case.

vabatta commented 7 years ago

@fbricon so we actually should use a maven or eclipse base project to get it working right? My JAVA_HOME is pointing to ~/.jenv/versions/1.8.0.102 which actually is the complete folder to JDK managed through jenv CLI command.

fbricon commented 7 years ago

I know I fixed the case when JAVA_HOME was not resolving paths starting with ~ recently (#28). Until the release later this week, can you try using an absolute path for JAVA_HOME?

And yes you currently need a Maven or Eclipse based project for the extension to be able to infer the project classpath. This requirement is stated in the extension description/README.

maxtar commented 7 years ago

@fbricon Thanx, waiting. :)

vabatta commented 7 years ago

@fbricon it's actually an absolute path, just used the ~ as shortcut, but I use it as /Users/vabatta/.... So, I probably need the Maven or Eclipse files to get the ext working (actually, I just opened the folder which contains only 3 Java files).

vabatta commented 7 years ago

So there won't be support to just Java files? I was using VS Code instead of a IDE solution due to have just some simple but complete autocomplete and syntax highlighting... I don't want to use a full-super-steroids-crappy-IDE, though it would do all as I don't want actually to install an App just for some easy Java homework 😋

linonetwo commented 7 years ago

@vabatta It only support maven now AFAIK

fbricon commented 7 years ago

@vabatta we're working on standalone java file support (#27)

linonetwo commented 7 years ago

@fbricon I think it's fine, though. Since in javascript world, we heavily rely on ESLint , which will only support full working directory opening, and don't work properly when opening single js file.

I just want some Gradle support.... Since react-native use Gradle instead of maven...

gorkem commented 7 years ago

@atang0404 Can you check the new 0.0.5 release if you have the same problem? Also please note that we have a new setting java.home to point to a Java SDK without the need for JAVA_HOME environment variable that may be interesting for you.

fernandocangussu commented 7 years ago

I'm with the same problem of @atang0404. But i'm using linux mint. I did set JAVA_HOME both ways, on linux and on vscode, but it doesn't work. [Error - 21:43:35] Starting client failed 13

gorkem commented 7 years ago

@atang0404 @fernandocangussu can you try the new 0.0.6 release. I only had a fedora to test but I think your issue may be resolved now.

fernandocangussu commented 7 years ago

Nothing here. I updated vscode and the extension, but the problem continues.

DanJ210 commented 7 years ago

I'm somewhat new to this and learning. Would anyone be kind enough to briefly explain how I get to the JAVA_HOME part to add my install path of the JDK? I can create a launch.json file but it gives me several choices and I'm not sure which I'm supposed to be choosing. Any help for a beginner would be much appreciated. I am currently a programming student but I've never had to set things up like this before. I have gotten some working like PHP, C#, JavaScript... This ones proving difficult! In the end, I am trying to open a .java file by itself so I know that it shouldn't work, I'm only trying to get up to speed on the JAVA_HOME. Thanks in advance.

Oh and I do have eclipse projects that I have made from a Java class so if I could figure out the JAVA_HOME thing, then I should be able to debug those eclipse projects...

YuvaAthur commented 7 years ago

Hi, I picked up the output of /usr/libexec/java_home and set "java.home": "/Library/Java/JavaVirtualMachines/jdk1.8.0_111.jdk/Contents/Home" in javaconfig.json setting.json

Still I get the error that java.home is not set right.

I have tried: a) uninstalling and reinstalling Java Extension b) several restarts of VS Code c) I keep getting thums down with no log :(! d) Java server is not able to start on the client. I have no clue how to fix it after searching for solutions on the web.

Environment: Mac OS X 10.11.6 | VS Code 1.7.1 | RedHat extension downloaded and applied on Nov 15th.

For the solution, I want clear instructions and samples - I find documentation rather hard to follow since there are very few examples on how the changes look in a real system.

Thanks for this! I enjoy working with VS Code and so would like to use for Java projects too.

Regards, Yuva

gorkem commented 7 years ago

@YuvaAthur thumbsdown usually means that your server is working but your project can not be recognized. Are you using a maven based project? The currently released version only supports maven.

We are aware that we are thin on documentation at the moment. We have started to write some, it is very early work but may help.

jamesskyoung commented 7 years ago

Quite like VSCode... installed it for my NodeJS projects -- and quite impressed. Works very well including the NodeJS debugging. Thought I'd try it out for Java.

It works.. but need to be able to define a build path a la Eclipse etc... We don't use Maven ... Doesn't look like that is supported? So looks like I'm stuck with Eclipse.. not a bad thing.. just prefer the Editor and speed of VSCode.

YuvaAthur commented 7 years ago

@gorkem - Thanks! I created a maven project in Eclipse and used it in VS Code. I got a ThumbsUp! Yay!

Now, eclipse has a simple pom.xml and a detailed pom.xml that is generated on the fly. What level of detail does VS Code Java project expect?

(BTW, the project is not compiling in eclipse - there are other issues to fix. I am working on it. Once I can get the project to compile, I shall test it in VS Code.)

gorkem commented 7 years ago

@YuvaAthur You do not need to have anything special on pom.xml for this extension. If you have a thumbs up that means the extension is able to recognize your project.

ryanstinson commented 7 years ago

Ubuntu 14.04 Version 1.9.1 Commit f9d0c687ff2ea7aabd85fb9a43129117c0ecf519 Date 2017-02-08T23:29:12.221Z Shell 1.4.6 Renderer 53.0.2785.143 Node 6.5.0

I am getting error after "Completing Java Installation" Error occurs "Couldn't start client Language Support for Java". The config_linux directory includes a log with exception:

!SESSION 2017-02-13 09:23:33.173 ----------------------------------------------- eclipse.buildId=unknown java.version=1.8.0_121 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line arguments: -data /home/ryanstinson/.config/Code/User/workspaceStorage/bc293bac07e5fda7793c38d73e44e662/redhat.java/jdt_ws

!ENTRY org.eclipse.osgi 4 0 2017-02-13 09:23:34.216 !MESSAGE Application error !STACK 1 java.lang.ExceptionInInitializerError at org.newsclub.net.unix.AFUNIXSocket.(AFUNIXSocket.java:36) at org.newsclub.net.unix.AFUNIXSocket.newInstance(AFUNIXSocket.java:54) at org.jboss.tools.vscode.java.internal.ConnectionStreamFactory$NamedPipeStreamProvider.getInputStream(ConnectionStreamFactory.java:56) at org.jboss.tools.vscode.java.internal.ConnectionStreamFactory.getInputStream(ConnectionStreamFactory.java:138) at org.jboss.tools.vscode.java.internal.JavaLanguageServerPlugin.startConnection(JavaLanguageServerPlugin.java:64) at org.jboss.tools.vscode.java.internal.JavaLanguageServerPlugin.startLanguageServer(JavaLanguageServerPlugin.java:117) at org.jboss.tools.vscode.java.internal.LanguageServer.start(LanguageServer.java:26) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590) at org.eclipse.equinox.launcher.Main.run(Main.java:1499) at org.eclipse.equinox.launcher.Main.main(Main.java:1472) Caused by: java.lang.IllegalStateException: java.lang.reflect.InvocationTargetException at org.newsclub.net.unix.NativeUnixSocket.(NativeUnixSocket.java:42) ... 20 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.newsclub.net.unix.NativeUnixSocket.(NativeUnixSocket.java:35) ... 20 more Caused by: java.lang.RuntimeException: Library 'libjunixsocket-native-2.0.4.so' not found! at org.newsclub.net.unix.NarSystem.getLibPath(NarSystem.java:132) at org.newsclub.net.unix.NarSystem.loadLibrary(NarSystem.java:36) ... 25 more

fbricon commented 7 years ago

Seems you need to install the native JNI libraries 1st. https://code.google.com/archive/p/junixsocket/wikis/GettingStarted.wiki.

For me, it works OOTB on ubuntu 16.10

ryanstinson commented 7 years ago

Thanks @fbricon - It seems the libs at that link are 1.x and the extension is looking for 2.0.4.

I don't see anyway to get the "libjunixsocket-native-2.0.4.so" it is looking for. Any help would be greatly appreciated.

fbricon commented 7 years ago

I don't know the answer to that, maybe @kohlschuetter can help?

ryanstinson commented 7 years ago

I was able to get the lib installed from maven repo. ldconfig shows the lib:

libjunixsocket-native-2.0.4.so (libc6,x86-64) => /usr/lib/libjunixsocket-native-2.0.4.so

But still the same error persists. Any help at this point?

ryanstinson commented 7 years ago

After digging a bit more, I found that the junix jar files are installed along side the org.eclipse.osgi libs. So, for whatever reason, the 'native-lib-loader' package cannot load the jar file and its embedded libjunixsocket-native-2.0.4.so library.

ryanstinson commented 7 years ago

@kohlschuetter any ideas?

kamtungc commented 7 years ago

I got the "Couldn't start client Language Support for Java" error on my Windows OS. I've followed all the steps in this discussion.

In Visual Studio Code "java.home": "C:\Progra~1\Java\jdk1.8.0_121" OR "java.home": "C:\Program Files\Java\jdk1.8.0_121"

In System: JAVA_HOME=C:\Program Files\Java\jdk1.8.0_121

I am using Visual Studio Code in Windows 10 partition on my Mac Pro machine.

Is there any debug log from this extension to check what the actual problem is?

ryanstinson commented 7 years ago

In the vs code extension directory "%USERPROFILE%.vscode\extensions" on windows, navigate to the red hat plugin/config_windows/server directory. Within that directory will be any logs associated with starting the plugin.

kamtungc commented 7 years ago

I have .vscode\extensions\redhat.java-0.0.10\server\config_win\config.ini only.

And, finally, I found the issue. It looks like the extension could not start correctly because of "java.jdt.ls.vmargs". "lombok.jar" is not correct. Now I can start the extension! Thanks!

"java.home": "c:\\Program Files\\Java\\jdk1.8.0_121",
"java.jdt.ls.vmargs": "-javaagent:C:\\codes\\libs\\java\\lombok.jar -Xbootclasspath/a:C:\\codes\\libs\\java\\lombok.jar"

I just followed https://github.com/redhat-developer/vscode-java/wiki/Lombok-support to add lombok.jar.

bluejekyll commented 7 years ago

I'm also experiencing the libjunixsocket-native-2.0.4.so issue. I extracted the .so from the jar, checked dependencies:

$ ldd libjunixsocket-native-2.0.4.so 
        linux-vdso.so.1 =>  (0x00007ffd1b4ce000)
    libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fc34d71d000)
    libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fc34d417000)
    libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fc34d201000)
    libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fc34ce39000)
    /lib64/ld-linux-x86-64.so.2 (0x00007fc34dc25000)

All of those exist on the system. In my case the specific error is a little different:

Caused by: java.lang.UnsatisfiedLinkError: /tmp/libjunixsocket-native-2.0.42440132215440112994.so: /tmp/libjunixsocket-native-2.0.42440132215440112994.so: failed to map segment from shared object: Operation not permitted

This is on an older version of ubuntu 14.04 (reasons...). My thought is there there may be reasons that the .so can't be loaded out of /tmp/ due to some mount restrictions on /tmp. I can't exec a shell script in /tmp for example. It's not mounted noexec though:

$ mount
...
/tmp on /var/tmp type none (rw,bind)

Any thoughts?

UPDATE: This did turn out to be a mount issue. I have a bind mount point for tmp, and the original mount point was noexec, removing that from fstab fixes the issue. I did look for an alternate way to change the tmp dir, but that wasn't obvious.

newxpp commented 7 years ago

can't run java! C:\Program Files (x86)\Java\jdk1.8.0_101

java version "1.8.0_101" Java(TM) SE Runtime Environment (build 1.8.0_101-b13) Java HotSpot(TM) Client VM (build 25.101-b13, mixed mode, sharing)

fbricon commented 7 years ago

@newxpp can you please enable logging so we can understand why the client fails to start?

limey-git commented 7 years ago

TL;DR — Download the junixsocket-parent-2.0.4 source, then build with maven.

I'm running a 32bit Ubuntu 12.04 guest on a VirtualBox VM. JDK 1.8.0_131-b11.

After downloading the VS Code version 1.12.0 yesterday, I got that same "Library 'libjunixsocket-native-2.0.4.so' not found!" error others reported.

My Ubuntu 12.04 VM is 32bit. The 'libjunixsocket-native-2.0.4.so' library that Microsoft distributes with the 32 bit version of Code 1.12.0, was built for a 64bit machine!

What fixed it for me, was this...

[ ] Backup all the jars in '_[your.home.dir]/.vscode/extensions/redhat.java-0.3.0/server/configlinux/org.eclipse.osgi/45/0/.cp/lib'
[ ] Download the junixsocket-parent-2.0.4 source from here, then untar it to wherever
[ ] cd to the parent project [junixsocket-junixsocket-parent-2.0.4]
[ ] Build with 'mvn package' [you might have to cd into junixsocket-native-common and junixsocket-native if they're not built by the parent]
[ ] Combine the contents of the following jars and folders into one single jar — then name that newly-created jar 'junixsocket-native-common-2.0.4.jar' [I stitched mine together manually. But you could probably hack the pom and have maven do it for you]

junixsocket-junixsocket-parent-2.0.4/junixsocket-native-common/target/META-INF
junixsocket-junixsocket-parent-2.0.4/junixsocket-native-common/target/junixsocket-native-common-2.0.4.jar
junixsocket-junixsocket-parent-2.0.4/junixsocket-native/target/META-INF
junixsocket-junixsocket-parent-2.0.4/junixsocket-native/target/junixsocket-native-2.0.4.jar
junixsocket-junixsocket-parent-2.0.4/junixsocket-native/target/nar/junixsocket-native-2.0.4-i386-Linux-gpp-jni/lib

Don't forget to include the MANIFEST.MF file.

This is what my merged 'junixsocket-native-common-2.0.4.jar' file contains...

lib/
lib/i386-Linux-gpp/
lib/i386-Linux-gpp/jni/
lib/i386-Linux-gpp/jni/history.xml
lib/i386-Linux-gpp/jni/libjunixsocket-native-2.0.4.so
META-INF/MANIFEST.MF
META-INF/maven/
META-INF/maven/com.kohlschutter.junixsocket/
META-INF/maven/com.kohlschutter.junixsocket/junixsocket-native/
META-INF/maven/com.kohlschutter.junixsocket/junixsocket-native-common/
META-INF/maven/com.kohlschutter.junixsocket/junixsocket-native-common/pom.properties
META-INF/maven/com.kohlschutter.junixsocket/junixsocket-native-common/pom.xml
META-INF/maven/com.kohlschutter.junixsocket/junixsocket-native/pom.properties
META-INF/maven/com.kohlschutter.junixsocket/junixsocket-native/pom.xml
META-INF/nar/
META-INF/nar/com.kohlschutter.junixsocket/
META-INF/nar/com.kohlschutter.junixsocket/junixsocket-native/
META-INF/nar/com.kohlschutter.junixsocket/junixsocket-native/nar.properties
org/
org/newsclub/
org/newsclub/net/
org/newsclub/net/jni/
org/newsclub/net/jni/DummyClass.class
org/newsclub/net/unix/
org/newsclub/net/unix/NarSystem.class

[ ] replace '_[your.home.dir]/.vscode/extensions/redhat.java-0.3.0/server/configlinux/org.eclipse.osgi/45/0/.cp/lib/junixsocket-native-common-2.0.4.jar' with the one you just built from the contents of all those other things.
[ ] replace '_[your.home.dir]/.vscode/extensions/redhat.java-0.3.0/server/configlinux/org.eclipse.osgi/45/0/.cp/lib/junixsocket-common-2.0.4.jar' with the one you built with maven '[junixsocket-junixsocket-parent-2.0.4/junixsocket-common/target/junixsocket-common-2.0.4.jar]'

Phewwww! What a faff just to install an IDE! That says a lot about Microsoft's commitment to *nix support. Ay?

fbricon commented 7 years ago

Discussion about 32bits junixsocket moved to #201

igor-kudryashov commented 7 years ago

I just installed VSCode v. 1.12.2 and "Language Support for Java(TM) by Red Hat" plugin v. 0.4.0. I have the same error "Couldn't start client Language Support for Java". I set up java.home parameter in VSCode. This does not solve the problem. I set up JAVA_HOME Windows variable to same folder. This does not solve the problem, too. I deleted java.home setting from VSCode. And here's a miracle! Everything worked. So, we have a problem with incorrect work java.home inside plugin.

fbricon commented 7 years ago

@igor-kudryashov can you please enable logging so we can understand what's happening?

igor-kudryashov commented 7 years ago

@fbricon I'm sorry, I can not repeat this error. I guess I did something wrong before.

simonl65 commented 7 years ago

I eventually got this working in Windows with the following in vscode:

"java.home": '"C:\Program Files\Java\jdk1.8.0_131"'

NOTES:

Double back-slashes
Single quotes around the double-quotes (because the path has spaces).

HTH

cwainner commented 7 years ago

I recently started having this problem as well on Ubuntu. This is the Java error that I get from the error log:

!ENTRY org.eclipse.osgi 4 0 2017-08-03 16:43:44.686
!MESSAGE Application error
!STACK 1
org.eclipse.core.runtime.CoreException: Plug-in org.eclipse.jdt.ls.core was unable to load class org.eclipse.jdt.ls.core.internal.LanguageServer.
    at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
    at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:176)
    at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
    at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
    at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:191)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
Caused by: java.lang.ClassNotFoundException: An error occurred while automatically activating bundle org.eclipse.jdt.ls.core (47).
    at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:112)
    at org.eclipse.osgi.internal.loader.classpath.ClasspathManager.findLocalClass(ClasspathManager.java:529)
    at org.eclipse.osgi.internal.loader.ModuleClassLoader.findLocalClass(ModuleClassLoader.java:328)
    at org.eclipse.osgi.internal.loader.BundleLoader.findLocalClass(BundleLoader.java:368)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:446)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:395)
    at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:387)
    at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:150)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
    at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)
    at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
    ... 16 more
Caused by: org.osgi.framework.BundleException: Exception in org.eclipse.jdt.ls.core.internal.JavaLanguageServerPlugin.start() of bundle org.eclipse.jdt.ls.core.
    at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:800)
    at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:729)
    at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:933)
    at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:309)
    at org.eclipse.osgi.container.Module.doStart(Module.java:581)
    at org.eclipse.osgi.container.Module.start(Module.java:449)
    at org.eclipse.osgi.framework.util.SecureAction.start(SecureAction.java:468)
    at org.eclipse.osgi.internal.hooks.EclipseLazyStarter.postFindLocalClass(EclipseLazyStarter.java:103)
    ... 26 more
Caused by: java.lang.NoClassDefFoundError: org/eclipse/jdt/core/JavaCore
    at org.eclipse.jdt.ls.core.internal.preferences.PreferenceManager.initialize(PreferenceManager.java:52)
    at org.eclipse.jdt.ls.core.internal.preferences.PreferenceManager.<init>(PreferenceManager.java:43)
    at org.eclipse.jdt.ls.core.internal.JavaLanguageServerPlugin.start(JavaLanguageServerPlugin.java:101)
    at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:779)
    at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:772)
    ... 33 more

I double check my jdk installation and that seems to be correct. I've also tried the JAVA_HOME fix, but looking at the above error I think it might be something different. I should also note that I did recently update my jdk to 1.8.0_131, so maybe that might have borked something?

fbricon commented 7 years ago

That kind of NoClassDefFoundError is typical of OSGi bundle failing to load. Possibly, your workspace got borked. I suggest cleaning it up and trying again

redhat-developer / vscode-java

Language Support for Java(TM) by Red Hat - Couldn't start client Language Support for Java #45

can't run java! C:\Program Files (x86)\Java\jdk1.8.0_101

TL;DR — Download the junixsocket-parent-2.0.4 source, then build with maven.