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

[Marián Labuda (JIRA)]

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

Marián Labuda edited comment on JBDS-4181 at 3/16/17 5:12 AM:
--------------------------------------------------------------

As I said, it is edge case, when user upgrade OS. If you want to reproduce, install Fedora 23 (maybe the later one would work too), install the specified java version, then upgrade to Fedora 24 and then the issue happened. It's not easily reproducible.


was (Author: mlabuda):
As I said, it is edge case, when user upgrade OS. If you want to reproduce, install Fedora 24, install the specified java version, then upgrade to Fedora 25 and then the issue happened. It's not easily reproducible.

> 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, upstream
>    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
>             Fix For: 10.x
>
>
> 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)