[jbosstools-issues] [JBoss JIRA] (JBIDE-25556) OpenJDK9 + org.jboss.tools.common: java.lang.Exception: No valid JDK found

Josef Kopriva (JIRA) issues at jboss.org
Fri Jun 29 03:17:00 EDT 2018


     [ https://issues.jboss.org/browse/JBIDE-25556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josef Kopriva closed JBIDE-25556.
---------------------------------


Closing - no error is shown.

Verified in:
Red Hat Developer Studio
Version: 12.0.0.GA
Build id: GA-v20180626-0421-B2872
Build date: 20180626-0421

> OpenJDK9 + org.jboss.tools.common: java.lang.Exception: No valid JDK found 
> ---------------------------------------------------------------------------
>
>                 Key: JBIDE-25556
>                 URL: https://issues.jboss.org/browse/JBIDE-25556
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: common
>    Affects Versions: 4.5.2.AM3
>         Environment: FC27 + OpenJDK9
>            Reporter: Josef Kopriva
>            Assignee: Rob Stryker
>             Fix For: 4.5.3.AM3
>
>
> Error message from error log:
> {code:java}
> eclipse.buildId=11.2.0.AM3-v20180105-1612-B1822
> java.version=9.0.1
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments:  -product com.jboss.devstudio.core.product
> Command-line arguments:  -data file:/home/jkopriva/devstudio_B1822-Java9-2/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.common.jdt.debug
> Error
> Thu Jan 11 10:45:50 CET 2018
> 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.base/java.util.TimerThread.mainLoop(Timer.java:556)
> 	at java.base/java.util.TimerThread.run(Timer.java:506)
> {code}



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)


More information about the jbosstools-issues mailing list