[JBoss JIRA] (JBIDE-25616) [WATCHER] 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 closed JBIDE-25616.
---------------------------------
Closing, starting server adapter in debug is not without error.
Verified in:
Red Hat Developer Studio
Version: 12.9.0.AM1
Build id: AM1-v20180802-0119-B3094
Build date: 20180802-0119
> [WATCHER] 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: Dmitrii Bocharov
> Labels: docker_image, fis, upstream
> Fix For: 4.9.0.AM1
>
> Attachments: java, screenshot-1.png
>
>
> 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)
7 years, 8 months
[JBoss JIRA] (JBIDE-26281) get*LaunchAttributes methods return null
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26281?page=com.atlassian.jira.plugi... ]
Jan Richter updated JBIDE-26281:
--------------------------------
Description:
Created a WildFly 13 server adapter and got a server handle back.
Now when I call the following, I get null back (handle is a valid server handle in this case).
{noformat}server/getRequiredLaunchAttributes({id: handle.id, mode: 'run'}){noformat}
The same goes for server/getOptionalLaunchAttributes.
was:
Created a WildFly 13 server adapter and got a server handle back.
Now when I call the following, I get null back.
{noformat}server/getRequiredLaunchAttributes({id: handle.id, mode: 'run'}){noformat}
The same goes for server/getOptionalLaunchAttributes.
> get*LaunchAttributes methods return null
> ----------------------------------------
>
> Key: JBIDE-26281
> URL: https://issues.jboss.org/browse/JBIDE-26281
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-server-protocol
> Reporter: Jan Richter
> Assignee: Rob Stryker
>
> Created a WildFly 13 server adapter and got a server handle back.
> Now when I call the following, I get null back (handle is a valid server handle in this case).
> {noformat}server/getRequiredLaunchAttributes({id: handle.id, mode: 'run'}){noformat}
> The same goes for server/getOptionalLaunchAttributes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26281) get*LaunchAttributes methods return null
by Jan Richter (JIRA)
Jan Richter created JBIDE-26281:
-----------------------------------
Summary: get*LaunchAttributes methods return null
Key: JBIDE-26281
URL: https://issues.jboss.org/browse/JBIDE-26281
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: runtime-server-protocol
Reporter: Jan Richter
Created a WildFly 13 server adapter and got a server handle back.
Now when I call the following, I get null back.
{noformat}server/getRequiredLaunchAttributes({id: handle.id, mode: 'run'}){noformat}
The same goes for server/getOptionalLaunchAttributes.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26227) EAP compatibility test sometimes fails on runtime search dialog
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26227?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26227.
---------------------------------
Job is green, so closing.
> EAP compatibility test sometimes fails on runtime search dialog
> ---------------------------------------------------------------
>
> Key: JBIDE-26227
> URL: https://issues.jboss.org/browse/JBIDE-26227
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests, server
> Affects Versions: 4.9.0.AM1
> Reporter: Martin Malina
> Assignee: Josef Kopriva
> Fix For: 4.9.0.AM1
>
> Attachments: RuntimeTest.png
>
>
> dcihak of the EAP QE team has reported that the compatibility test they've been using started failing sometimes:
> https://eap-cp-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/...
> Build 18 failed on openjdk and build 19 failed on oracle jdk. So it only happens sometimes.
> Here's an example of the failure:
> https://eap-cp-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/...
> {code}
> Error Message
> No matching widget found with Matcher matching when all matchers match: [Matcher matching widget with the same type as or type extending class org.eclipse.swt.widgets.Label, Matcher matching widget which text matches: "Searching runtimes is finished."]
> class org.eclipse.swt.widgets.Shell[shell: 'Searching for runtimes...'] with text 'Searching for runtimes...'
> class org.eclipse.swt.widgets.Composite[shell: 'Searching for runtimes...']
> class org.eclipse.swt.widgets.Label[shell: 'Searching for runtimes...'] with text ''
> class org.eclipse.swt.widgets.Label[shell: 'Searching for runtimes...'] with label '' with text 'Searching /home/hudson/hudson_workspace/works...bot.itests/target/requirements/jboss-eap-7.1'
> class org.eclipse.swt.widgets.Tree[shell: 'Searching for runtimes...'] with label 'Searching /home/hudson/hudson_workspace/works...bot.itests/target/requirements/jboss-eap-7.1'
> class org.eclipse.swt.widgets.Label[shell: 'Searching for runtimes...'] with label 'Searching /home/hudson/hudson_workspace/works...bot.itests/target/requirements/jboss-eap-7.1' with text ''
> class org.eclipse.jface.dialogs.ProgressIndicator[shell: 'Searching for runtimes...'] with label ''
> class org.eclipse.swt.widgets.ProgressBar[shell: 'Searching for runtimes...']
> class org.eclipse.swt.widgets.ProgressBar[shell: 'Searching for runtimes...']
> class org.eclipse.swt.widgets.Button[shell: 'Searching for runtimes...'] with label '' with text 'Hide already created runtimes'
> class org.eclipse.swt.widgets.Button[shell: 'Searching for runtimes...'] with label '' with text 'Add runtime path to list of paths searchable on startup'
> class org.eclipse.jface.dialogs.ProgressIndicator[shell: 'Searching for runtimes...'] with label ''
> class org.eclipse.swt.widgets.ProgressBar[shell: 'Searching for runtimes...'] with label ''
> class org.eclipse.swt.widgets.ProgressBar[shell: 'Searching for runtimes...']
> class org.eclipse.swt.widgets.Label[shell: 'Searching for runtimes...'] with label '' with text ''
> class org.eclipse.swt.widgets.Composite[shell: 'Searching for runtimes...'] with label ''
> class org.eclipse.swt.widgets.Button[shell: 'Searching for runtimes...'] with label '' with text 'OK'
> class org.eclipse.swt.widgets.Button[shell: 'Searching for runtimes...'] with label '' with text 'Select All'
> class org.eclipse.swt.widgets.Button[shell: 'Searching for runtimes...'] with label '' with text 'Deselect All'
> class org.eclipse.swt.widgets.Button[shell: 'Searching for runtimes...'] with label '' with text 'Cancel'
> Stacktrace
> org.eclipse.reddeer.core.exception.CoreLayerException: No matching widget found with Matcher matching when all matchers match: [Matcher matching widget with the same type as or type extending class org.eclipse.swt.widgets.Label, Matcher matching widget which text matches: "Searching runtimes is finished."]
> class org.eclipse.swt.widgets.Shell[shell: 'Searching for runtimes...'] with text 'Searching for runtimes...'
> class org.eclipse.swt.widgets.Composite[shell: 'Searching for runtimes...']
> class org.eclipse.swt.widgets.Label[shell: 'Searching for runtimes...'] with text ''
> class org.eclipse.swt.widgets.Label[shell: 'Searching for runtimes...'] with label '' with text 'Searching /home/hudson/hudson_workspace/works...bot.itests/target/requirements/jboss-eap-7.1'
> class org.eclipse.swt.widgets.Tree[shell: 'Searching for runtimes...'] with label 'Searching /home/hudson/hudson_workspace/works...bot.itests/target/requirements/jboss-eap-7.1'
> class org.eclipse.swt.widgets.Label[shell: 'Searching for runtimes...'] with label 'Searching /home/hudson/hudson_workspace/works...bot.itests/target/requirements/jboss-eap-7.1' with text ''
> class org.eclipse.jface.dialogs.ProgressIndicator[shell: 'Searching for runtimes...'] with label ''
> class org.eclipse.swt.widgets.ProgressBar[shell: 'Searching for runtimes...']
> class org.eclipse.swt.widgets.ProgressBar[shell: 'Searching for runtimes...']
> class org.eclipse.swt.widgets.Button[shell: 'Searching for runtimes...'] with label '' with text 'Hide already created runtimes'
> class org.eclipse.swt.widgets.Button[shell: 'Searching for runtimes...'] with label '' with text 'Add runtime path to list of paths searchable on startup'
> class org.eclipse.jface.dialogs.ProgressIndicator[shell: 'Searching for runtimes...'] with label ''
> class org.eclipse.swt.widgets.ProgressBar[shell: 'Searching for runtimes...'] with label ''
> class org.eclipse.swt.widgets.ProgressBar[shell: 'Searching for runtimes...']
> class org.eclipse.swt.widgets.Label[shell: 'Searching for runtimes...'] with label '' with text ''
> class org.eclipse.swt.widgets.Composite[shell: 'Searching for runtimes...'] with label ''
> class org.eclipse.swt.widgets.Button[shell: 'Searching for runtimes...'] with label '' with text 'OK'
> class org.eclipse.swt.widgets.Button[shell: 'Searching for runtimes...'] with label '' with text 'Select All'
> class org.eclipse.swt.widgets.Button[shell: 'Searching for runtimes...'] with label '' with text 'Deselect All'
> class org.eclipse.swt.widgets.Button[shell: 'Searching for runtimes...'] with label '' with text 'Cancel'
> at org.eclipse.reddeer.common.wait.WaitUntil.throwWaitTimeOutException(WaitUntil.java:122)
> at org.eclipse.reddeer.common.wait.AbstractWait.timeoutExceeded(AbstractWait.java:207)
> at org.eclipse.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:151)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:132)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:97)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:64)
> at org.eclipse.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:50)
> at org.eclipse.reddeer.core.lookup.WidgetLookup.activeWidget(WidgetLookup.java:109)
> at org.eclipse.reddeer.core.lookup.WidgetLookup.activeWidget(WidgetLookup.java:87)
> at org.eclipse.reddeer.swt.widgets.AbstractWidget.<init>(AbstractWidget.java:76)
> at org.eclipse.reddeer.swt.widgets.AbstractControl.<init>(AbstractControl.java:38)
> at org.eclipse.reddeer.swt.impl.label.AbstractLabel.<init>(AbstractLabel.java:24)
> at org.eclipse.reddeer.swt.impl.label.DefaultLabel.<init>(DefaultLabel.java:102)
> at org.eclipse.reddeer.swt.impl.label.DefaultLabel.<init>(DefaultLabel.java:62)
> at org.eclipse.reddeer.swt.impl.label.DefaultLabel.<init>(DefaultLabel.java:52)
> at org.jboss.tools.as.ui.bot.itests.reddeer.ui.RuntimeDetectionPreferencePage$RuntimeSearchedFinished.test(RuntimeDetectionPreferencePage.java:70)
> at org.eclipse.reddeer.common.wait.WaitUntil.stopWaiting(WaitUntil.java:103)
> at org.eclipse.reddeer.common.wait.AbstractWait.wait(AbstractWait.java:147)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:132)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:97)
> at org.eclipse.reddeer.common.wait.AbstractWait.<init>(AbstractWait.java:64)
> at org.eclipse.reddeer.common.wait.WaitUntil.<init>(WaitUntil.java:50)
> at org.jboss.tools.as.ui.bot.itests.reddeer.ui.RuntimeDetectionPreferencePage.search(RuntimeDetectionPreferencePage.java:61)
> at org.jboss.tools.as.ui.bot.itests.reddeer.util.RuntimeDetectionUtility.addPath(RuntimeDetectionUtility.java:37)
> at org.jboss.tools.as.ui.bot.itests.reddeer.util.DetectRuntimeTemplate.detectRuntime(DetectRuntimeTemplate.java:37)
> at org.jboss.tools.as.ui.bot.itests.server.SingleServerRuntimeTest.checkCountAndGetServerName(SingleServerRuntimeTest.java:60)
> at org.jboss.tools.as.ui.bot.itests.server.SingleServerRuntimeTest.detect(SingleServerRuntimeTest.java:56)
> {code}
> And a screenshot:
> https://eap-cp-qe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/EAP7/view/...
> !RuntimeTest.png!
> One possible explanation is that sometimes it takes longer for the runtime to be found and that makes the test fail. If that's true, then some added wait may fix the problem.
> Keep in mind that we'll need this fix also for the photon stream (JBT 4.6.0), so I guess we'll need to bug Rob to create a maintenance branch from the 4.6.0.Final tag for this.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26173) Validation for 'oc executable location' in Preferences OpenShift 3 page does not allow to keep value empty
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26173?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26173.
---------------------------------
Issue is fixed.
Verified in:
Red Hat Developer Studio
Version: 12.9.0.AM1
Build id: AM1-v20180802-0119-B3094
Build date: 20180802-0119
> Validation for 'oc executable location' in Preferences OpenShift 3 page does not allow to keep value empty
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26173
> URL: https://issues.jboss.org/browse/JBIDE-26173
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.Final
> Reporter: Ondrej Dockal
> Assignee: Andre Dietisheim
> Fix For: 4.9.0.AM1
>
> Attachments: image-2018-07-09-18-20-57-878.png, image-2018-07-09-18-21-13-711.png, image-2018-07-09-18-21-33-723.png, image-2018-07-09-18-24-08-509.png
>
>
> When user chooses Preferences -> Jboss Tools -> OpenShift 3 and does nothing (ie. when one just clicked to wrong page), the page cannot be changed, 'Could not accept changes' dialog pops up and user must cancel Preferences dialog.
> I suggest to not validate empty oc location.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months