[JBoss JIRA] (JBIDE-25556) OpenJDK9 + org.jboss.tools.common: java.lang.Exception: No valid JDK found
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25556?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25556:
-------------------------------
Fix Version/s: 4.5.3.AM1
(was: 4.5.x)
> 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.AM1
>
>
> 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)
8 years, 2 months
[JBoss JIRA] (JBIDE-25295) Cannot use minishift binary instead of CDK in CDK server adapter in IDE
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25295?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25295:
-------------------------------
Fix Version/s: 4.5.3.AM1
(was: 4.5.x)
> Cannot use minishift binary instead of CDK in CDK server adapter in IDE
> -----------------------------------------------------------------------
>
> Key: JBIDE-25295
> URL: https://issues.jboss.org/browse/JBIDE-25295
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.1.Final
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.5.3.AM1
>
> Attachments: Screenshot_20171025_134414.png
>
>
> I am curious what if user will want to use upstream minishift binary for CDK 3.x (3.2+) server adapter. It is not possible now.
> Is there a reason for not allowing user to use upstream minishift binary? Before we did not distinguish between CDK 3.1 and 3.2, it was possible in my opinion. We lost this option when new adapter was added and we started to check CDK v.3.x.x version string for two CDK 3.1 and CDK 3.2 binaries.
> [~rob.stryker] [~jeffmaury] [~mmalina] WDYT?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25295) Cannot use minishift binary instead of CDK in CDK server adapter in IDE
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25295?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25295:
-------------------------------
Sprint: devex #142 December 2017, devex #144 January 2018 (was: devex #142 December 2017)
> Cannot use minishift binary instead of CDK in CDK server adapter in IDE
> -----------------------------------------------------------------------
>
> Key: JBIDE-25295
> URL: https://issues.jboss.org/browse/JBIDE-25295
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk
> Affects Versions: 4.5.1.Final
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.5.3.AM1
>
> Attachments: Screenshot_20171025_134414.png
>
>
> I am curious what if user will want to use upstream minishift binary for CDK 3.x (3.2+) server adapter. It is not possible now.
> Is there a reason for not allowing user to use upstream minishift binary? Before we did not distinguish between CDK 3.1 and 3.2, it was possible in my opinion. We lost this option when new adapter was added and we started to check CDK v.3.x.x version string for two CDK 3.1 and CDK 3.2 binaries.
> [~rob.stryker] [~jeffmaury] [~mmalina] WDYT?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25616) Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25616:
-------------------------------
Fix Version/s: 4.5.3.AM1
(was: 4.5.3.AM2)
> Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-25616
> URL: https://issues.jboss.org/browse/JBIDE-25616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Fix For: 4.5.3.AM1
>
> Attachments: java
>
>
> Starting of server ends with error:
> {code:java}
> eclipse.buildId=11.2.0.GA-v20180122-2025-B1884
> java.version=1.8.0_151
> 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_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Jan 24 11:21:45 CET 2018
> Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com)
> org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25616) Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-25616:
---------------------------------------
Hi [~aurelien.pupier], thanks for link to your comment.
I am using Fuse tooling from Central version: 10.2.0.v20180117-1512 and when I have tried Camel version 2.18.1.redhat-000021 I get this errors (during starting and restarting server adapter):
{code:java}
eclipse.buildId=11.2.0.GA-v20180122-2025-B1884
java.version=1.8.0_151
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_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
org.jboss.tools.openshift.core
Info
Wed Jan 24 14:56:54 CET 2018
Could not find any route for resource camel-ose-springboot-xml
{code}
{code:java}
eclipse.buildId=11.2.0.GA-v20180122-2025-B1884
java.version=1.8.0_151
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_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
org.jboss.tools.openshift.core
Error
Wed Jan 24 14:57:03 CET 2018
Syncing com.openshift.restclient.capability.resources.IRSyncable$PodPeer@123ec2be to com.openshift.restclient.capability.resources.IRSyncable$LocalPeer@66e015e5 failed: rsync: change_dir "/deployments/BOOT-INF/classes" failed: No such file or directory (2)
command terminated with exit code 23
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1650) [Receiver=3.1.2]
error: exit status 23
{code}
{code:java}
eclipse.buildId=11.2.0.GA-v20180122-2025-B1884
java.version=1.8.0_151
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_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
org.jboss.tools.openshift.core
Error
Wed Jan 24 14:57:03 CET 2018
Error while publishing server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com) (2). Could not sync all pods to folder /home/jkopriva/devstudio_B1884_jiras/workspace/.metadata/.plugins/org.jboss.ide.eclipse.as.core/testfuse@camel-ose-springboot-xml/deploy
{code}
> Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-25616
> URL: https://issues.jboss.org/browse/JBIDE-25616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Fix For: 4.5.3.AM1
>
> Attachments: java
>
>
> Starting of server ends with error:
> {code:java}
> eclipse.buildId=11.2.0.GA-v20180122-2025-B1884
> java.version=1.8.0_151
> 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_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Jan 24 11:21:45 CET 2018
> Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com)
> org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months
[JBoss JIRA] (JBIDE-25616) Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25616?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25616:
-------------------------------
Story Points: 15
> Server Adapter: Cannot start remote debugger for Fuse app deployed on open.paas.redhat.com
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-25616
> URL: https://issues.jboss.org/browse/JBIDE-25616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.5.2.Final
> Environment: F27 + open.paas.redhat.com + Red Hat JBoss Developer Studio Build id: GA-v20180122-2025-B1884
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Fix For: 4.5.3.AM2
>
> Attachments: java
>
>
> Starting of server ends with error:
> {code:java}
> eclipse.buildId=11.2.0.GA-v20180122-2025-B1884
> java.version=1.8.0_151
> 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_B1884_jiras/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.openshift.core
> Error
> Wed Jan 24 11:21:45 CET 2018
> Could not launch server camel-ose-springboot-xml (Service) at OpenShift 3 (open.paas.redhat.com)
> org.eclipse.core.runtime.CoreException: Could not start remote debugger to (forwarded) port 45933 on localhost
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:670)
> at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.toCoreException(OpenShiftServerUtils.java:674)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.attachRemoteDebugger(OpenShiftLaunchController.java:404)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.access$1(OpenShiftLaunchController.java:387)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:272)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:238)
> at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:174)
> at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:100)
> at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731)
> at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566)
> at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502)
> at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 2 months