[JBoss JIRA] (JBIDE-21619) Accessing CDK server raises this exception: Problems occurred when invoking code from plug-in: "org.eclipse.jface".
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21619?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21619:
----------------------------------------
Looks like a duplicate of JBIDE-21613
> Accessing CDK server raises this exception: Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21619
> URL: https://issues.jboss.org/browse/JBIDE-21619
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Environment: JBoss Developer Studio
> Version: 9.1.0.Beta2
> Build id: Beta2-v20160127-2213-B262
> Build date: 20160127-2213
> RHEL7
> Java 1.8
> Reporter: Len DiMaggio
>
> To recreate the error:
> 1) Create a new CDL server runtime - I used CDK2, Beta4
> 2) In the server explorer, start the server, and then left click on the running server
> This message is generated:
> Problems occurred when invoking code from plug-in: "org.eclipse.jface".
> And, this exception is raised:
> java.lang.NullPointerException
> at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.findDockerConnection(CDKDockerUtility.java:53)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:111)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:188)
> at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85)
> at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:203)
> at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144)
> at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197)
> at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228)
> at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:461)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257)
> at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
> at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21619) Accessing CDK server raises this exception: Problems occurred when invoking code from plug-in: "org.eclipse.jface".
by Len DiMaggio (JIRA)
Len DiMaggio created JBIDE-21619:
------------------------------------
Summary: Accessing CDK server raises this exception: Problems occurred when invoking code from plug-in: "org.eclipse.jface".
Key: JBIDE-21619
URL: https://issues.jboss.org/browse/JBIDE-21619
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: cdk
Affects Versions: 4.3.1.Beta2
Environment: JBoss Developer Studio
Version: 9.1.0.Beta2
Build id: Beta2-v20160127-2213-B262
Build date: 20160127-2213
RHEL7
Java 1.8
Reporter: Len DiMaggio
To recreate the error:
1) Create a new CDL server runtime - I used CDK2, Beta4
2) In the server explorer, start the server, and then left click on the running server
This message is generated:
Problems occurred when invoking code from plug-in: "org.eclipse.jface".
And, this exception is raised:
java.lang.NullPointerException
at org.jboss.tools.openshift.cdk.server.core.internal.listeners.CDKDockerUtility.findDockerConnection(CDKDockerUtility.java:53)
at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInDockerViewAfterStartupAction.adaptToViewItem(CDKActionProvider.java:111)
at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.accept(CDKActionProvider.java:188)
at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.selectionChanged(AbstractServerAction.java:85)
at org.jboss.tools.openshift.cdk.server.ui.internal.view.CDKActionProvider$ShowInViewAfterStartupAction.selectionChanged(CDKActionProvider.java:203)
at org.eclipse.ui.actions.SelectionProviderAction.selectionChanged(SelectionProviderAction.java:144)
at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160)
at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197)
at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228)
at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:461)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257)
at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21614) OpenShift connection is not created when CDK server starts on Windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21614?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21614:
--------------------------------------
Assignee: Rob Stryker
> OpenShift connection is not created when CDK server starts on Windows
> ---------------------------------------------------------------------
>
> Key: JBIDE-21614
> URL: https://issues.jboss.org/browse/JBIDE-21614
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> I'm testing the latest JBDS 9.1.0.CR1 nightly build + CDK from the PDK installer.
> When I create and start CDK server on my Ubuntu it creates OpenShift connection.
> When I do the same (same CDK, same JBDS build) on Windows, vargrant starts successfully (I can access OS web console etc.) but the OpenShift connection is not created in JBDS.
> It worked before (sometime ago on a different installation).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21614) OpenShift connection is not created when CDK server starts on Windows
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21614?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21614:
-----------------------------------
Priority: Blocker (was: Critical)
> OpenShift connection is not created when CDK server starts on Windows
> ---------------------------------------------------------------------
>
> Key: JBIDE-21614
> URL: https://issues.jboss.org/browse/JBIDE-21614
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> I'm testing the latest JBDS 9.1.0.CR1 nightly build + CDK from the PDK installer.
> When I create and start CDK server on my Ubuntu it creates OpenShift connection.
> When I do the same (same CDK, same JBDS build) on Windows, vargrant starts successfully (I can access OS web console etc.) but the OpenShift connection is not created in JBDS.
> It worked before (sometime ago on a different installation).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21614) OpenShift connection is not created when CDK server starts on Windows
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21614?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21614:
-------------------------------------
Windows is blocking on this: http://fpaste.org/317246/35293114/
Basically, the error stream is indicating something requiring user interaction and we're not handling it properly, so the thread blocks while trying to read sysout that never comes, but since the process never dies, the stream never closes.
> OpenShift connection is not created when CDK server starts on Windows
> ---------------------------------------------------------------------
>
> Key: JBIDE-21614
> URL: https://issues.jboss.org/browse/JBIDE-21614
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Alexey Kazakov
> Priority: Critical
> Fix For: 4.3.1.CR1
>
>
> I'm testing the latest JBDS 9.1.0.CR1 nightly build + CDK from the PDK installer.
> When I create and start CDK server on my Ubuntu it creates OpenShift connection.
> When I do the same (same CDK, same JBDS build) on Windows, vargrant starts successfully (I can access OS web console etc.) but the OpenShift connection is not created in JBDS.
> It worked before (sometime ago on a different installation).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21616:
-------------------------------------
This is an upstream error. Simply resizing the window makes all widgets show.
> Main tab for CDK launch configuration is not whole by default
> -------------------------------------------------------------
>
> Key: JBIDE-21616
> URL: https://issues.jboss.org/browse/JBIDE-21616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Environment: Fedora 22, GTK3
> Reporter: Marián Labuda
> Attachments: after.png, before.png
>
>
> In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available.
> !before.png!
> After switching to Environment tab and back, Working directory and Arguments widgets become available.
> !after.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21617) Import wizard: Build config should be preselected if service in Explorer is selected
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21617?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-21617:
-----------------------------------
Assignee: Fred Bricon
> Import wizard: Build config should be preselected if service in Explorer is selected
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21617
> URL: https://issues.jboss.org/browse/JBIDE-21617
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Labels: explorer, import_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> When I am trying to import an OpenShift application via context menu of a service the Import OpenShift application wizard is opened, but first project is preselected in the wizard. It would be nice, if appropriate build config would be preselected if I have a selected service in OpenShift epxlorer view and opening Import OpenShift application wizard via its context menu.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21617) Import wizard: Build config should be preselected if service in Explorer is selected
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21617?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21617:
-----------------------------------------------
[~adietish], please take a look at pull request https://github.com/jbosstools/jbosstools-openshift/pull/933
In explorer, it is deployment node that represents service with other resources, it adapts to a build config, but only if there is exactly one. Otherwise, the project for the service may be preselected.
> Import wizard: Build config should be preselected if service in Explorer is selected
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-21617
> URL: https://issues.jboss.org/browse/JBIDE-21617
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: explorer, import_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> When I am trying to import an OpenShift application via context menu of a service the Import OpenShift application wizard is opened, but first project is preselected in the wizard. It would be nice, if appropriate build config would be preselected if I have a selected service in OpenShift epxlorer view and opening Import OpenShift application wizard via its context menu.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-20447) 2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20447?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov reassigned JBIDE-20447:
----------------------------------------------
Assignee: Konstantin Marmalyukov
> 2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component
> ------------------------------------------------------------------
>
> Key: JBIDE-20447
> URL: https://issues.jboss.org/browse/JBIDE-20447
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: common/jst/core
> Affects Versions: 4.3.0.CR1
> Reporter: Nick Boldt
> Assignee: Konstantin Marmalyukov
> Labels: testfailure
> Fix For: 4.4.x
>
>
> *2 Test Failure(s) in JBIDE 4.3.0.CR1 for common/jst/core component:*
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_mast...
> # [org.jboss.tools.foundation.ui.test.BrowserUtilTest|https://jenkins.mw.lab...] (failing for 11 builds)
> # [org.jboss.tools.foundation.ui.test.BrowserUtilTest|https://jenkins.mw.lab...] (failing for 11 builds)
> [Search for Test Failure JIRAs in JBIDE 4.3.0.CR1 for common/jst/core component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.foundation.ui.test.BrowserUtilTest : testCreateBrowserOrLink{color} (failing for 11 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master/786/testReport/org.jboss.tools.foundation.ui.test/BrowserUtilTest/testCreateBrowserOrLink}
> <case>
> <age>11</age>
> <className>org.jboss.tools.foundation.ui.test.BrowserUtilTest</className>
> <duration>0.268</duration>
> <errorStackTrace>java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertTrue(Assert.java:52)
> at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowserOrLink(BrowserUtilTest.java:51)
> </errorStackTrace>
> <failedSince>776</failedSince>
> <name>testCreateBrowserOrLink</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
> * {color:red}org.jboss.tools.foundation.ui.test.BrowserUtilTest : testCreateBrowser{color} (failing for 11 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-base_master/786/testReport/org.jboss.tools.foundation.ui.test/BrowserUtilTest/testCreateBrowser}
> <case>
> <age>11</age>
> <className>org.jboss.tools.foundation.ui.test.BrowserUtilTest</className>
> <duration>0.0030</duration>
> <errorStackTrace>java.lang.AssertionError: null
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertNotNull(Assert.java:712)
> at org.junit.Assert.assertNotNull(Assert.java:722)
> at org.jboss.tools.foundation.ui.test.BrowserUtilTest.testCreateBrowser(BrowserUtilTest.java:32)
> </errorStackTrace>
> <failedSince>776</failedSince>
> <name>testCreateBrowser</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> </case>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months