[jbosstools-issues] [JBoss JIRA] (JBDS-4181) No valid JDK found

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-4181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13324015#comment-13324015 ] 

Nick Boldt commented on JBDS-4181:
----------------------------------

With which JDK did you START Eclipse? Where's it installed? Do you also have JDK 7 or 9 installed? What's in alternatives for java?

{code}
$➔ alternatives --display java

Current `best' version is /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/jre/bin/java.

$➔ which java
alias java='/usr/bin/java'
	/usr/bin/java

$➔ whereis java
java: /usr/bin/java /usr/lib/java /etc/java /usr/share/java /opt/jdk1.8.0_102/bin/java /opt/jdk-9-ea+140/bin/java /usr/share/man/man1/java.1.gz

$➔ java -version
openjdk version "1.8.0_65"
OpenJDK Runtime Environment (build 1.8.0_65-b17)
OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
{code}

What happens if you start eclipse/devstudio using ./eclipse -vm /path/to/java/bin/folder ?


> No valid JDK found
> ------------------
>
>                 Key: JBDS-4181
>                 URL: https://issues.jboss.org/browse/JBDS-4181
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Bug
>          Components: common
>    Affects Versions: 10.2.0.GA
>         Environment: Fedora 24,
> openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> OpenJDK 64-Bit Server VM (build 25.102-b14, mixed mode)
>            Reporter: Marián Labuda
>            Assignee: Rob Stryker
>
> When I start latest DevStudio 10.2.0.GA build ID GA-v20161116-0039-B6472, I get following error in error log 
> {code}
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> java.lang.Exception: No valid JDK found in your eclipse workspace for JBoss Tools Launching Support. Please add one at Window -> Preferences -> Installed JREs.
> 	at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findFirstValidVMInstall(Tools.java:275)
> 	at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findSecondaryVMInstall(Tools.java:432)
> 	at org.jboss.tools.common.jdt.debug.tools.internal.Tools.findHomeDirectoryToAddToClasspath(Tools.java:417)
> 	at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsJar(Tools.java:146)
> 	at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getToolsLoader(Tools.java:121)
> 	at org.jboss.tools.common.jdt.debug.tools.internal.Tools.reset(Tools.java:114)
> 	at org.jboss.tools.common.jdt.debug.tools.internal.Tools.<init>(Tools.java:82)
> 	at org.jboss.tools.common.jdt.debug.tools.internal.Tools.getInstance(Tools.java:73)
> 	at org.jboss.tools.common.jdt.debug.tools.ToolsCore.getActiveProcessIds(ToolsCore.java:179)
> 	at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler.updatesActiveJvms(JvmAttachHandler.java:100)
> 	at org.jboss.tools.jmx.jvmmonitor.internal.tools.JvmAttachHandler$1.run(JvmAttachHandler.java:78)
> 	at java.util.TimerThread.mainLoop(Timer.java:555)
> 	at java.util.TimerThread.run(Timer.java:505)
> {code}



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)