[JBoss JIRA] (JBIDE-24042) Provide bigger dialog for adding header of a Jolokia JMX Connection
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24042?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-24042.
---------------------------------
Both size and header are fixed. Verified in JBT 4.4.4.AM2.
> Provide bigger dialog for adding header of a Jolokia JMX Connection
> -------------------------------------------------------------------
>
> Key: JBIDE-24042
> URL: https://issues.jboss.org/browse/JBIDE-24042
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jmx
> Affects Versions: 4.4.3.Final
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.4.AM2, 4.5.0.AM1
>
> Attachments: image-2017-03-08-10-23-23-647.png, image-2017-03-08-10-23-23-647.png
>
>
> currently, even the title is not completely visible:
> !image-2017-03-08-10-23-23-647.png|thumbnail! !image-2017-03-08-10-23-23-647.png|thumbnail!
> would be nice to have more space for fields too, at least to file some token stuff which would be quite a classical header that will be provided. If there are Jolokia expert would be nice to ask them the maximum size of common values to determine the best size
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24139) Cannot "connect debugger" from JMX Navigator if a project is closed
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24139?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-24139.
---------------------------------
I could reproduce the issue in devstudio 10.4.0.AM1.
In JBT 4.4.4.AM2 I no longer get the error about the closed project, just this:
{code}
!ENTRY org.eclipse.jdt.launching 4 113 2017-04-06 13:48:19.715
!MESSAGE Failed to connect to remote VM. Connection refused.
!STACK 0
java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at java.net.Socket.<init>(Socket.java:434)
at java.net.Socket.<init>(Socket.java:211)
at org.eclipse.jdi.internal.connect.SocketTransportService$2.run(SocketTransportService.java:148)
at java.lang.Thread.run(Thread.java:745)
{code}
Which I guess is expected since I just had a WildFly 10 running in debug mode.
> Cannot "connect debugger" from JMX Navigator if a project is closed
> -------------------------------------------------------------------
>
> Key: JBIDE-24139
> URL: https://issues.jboss.org/browse/JBIDE-24139
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jmx
> Affects Versions: 4.4.3.Final, 4.4.4.AM1
> Reporter: Aurélien Pupier
> Assignee: Aurélien Pupier
> Fix For: 4.4.4.AM2
>
>
> {noformat}
> !ENTRY org.jboss.tools.jmx.ui 4 0 2017-03-29 14:37:58.659
> !MESSAGE Resource '/217' is not open.
> !STACK 1
> org.eclipse.core.internal.resources.ResourceException: Resource '/217' is not open.
> at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:144)
> at org.eclipse.core.internal.resources.Project.hasNature(Project.java:516)
> at org.jboss.tools.jmx.ui.internal.actions.ConnectDebuggerAction.run(ConnectDebuggerAction.java:59)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:565)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:397)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4418)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4236)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3824)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> !SUBENTRY 1 org.eclipse.core.resources 4 372 2017-03-29 14:37:58.659
> !MESSAGE Resource '/217' is not open.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24006) Wildfly server adapter does not report error and works inconsistently
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24006?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-24006.
---------------------------------
This seems to work as expected. I was unable to get the conflict, because the class bound the port on some other host than 127.0.0.1 or my hostname. But if I used 0.0.0.0 for the WildFly server (both -b and -Djboss.bind.address.management), I could see the confict.
In the case of WildFly 11, the server would stop on its own and the new error was thrown in the error log. In the case of WildFly 10, the server will not stop and will remain Started, but you can see the errors in the server log. When I used port 9999 instead of 9990, I could still get the new error with WildFly 11 as expected, but the tooling seem to have a problem with non-standard management ports - I created a new JIRA for that: JBIDE-24233
Closing.
> Wildfly server adapter does not report error and works inconsistently
> ---------------------------------------------------------------------
>
> Key: JBIDE-24006
> URL: https://issues.jboss.org/browse/JBIDE-24006
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.3.Final
> Reporter: Jeff MAURY
> Assignee: Rob Stryker
> Labels: server, server_adapter, wildfly
> Fix For: 4.4.4.AM2
>
>
> If Wildfly uses 9999 as the management port, then no error is reported but the adapter does not work.
> Here is an except we've got from the customer:
> {noformat}
> I have an important update on this. I think it's mostly good news.
> I debugged the issue via a virtual session with the person that develops the WildFly plugin for NetBeans. What we found out is that the management port I was using, 9999, conflicts with Netty. For context, I had to specify a port override since 9990 commonly conflicts with NVIDIA drivers on Windows. As soon as I used a port other than 9999 and 9990 everything worked absolutely perfectly. As soon as I switch to 9999 everything basically breaks without a real error message indicating the underlying issue. Using 9990 on the other hand clearly indicated a port conflict.
> I tried the same thing on Eclipse with exactly the same results.
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24233) Server fails to stop when using non-standard management port
by Martin Malina (JIRA)
Martin Malina created JBIDE-24233:
-------------------------------------
Summary: Server fails to stop when using non-standard management port
Key: JBIDE-24233
URL: https://issues.jboss.org/browse/JBIDE-24233
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.4.4.AM2
Reporter: Martin Malina
Assignee: Rob Stryker
While testing JBIDE-24006 I found a bug (I think).
When you change the management port in standalone.xml from 9990 to 9999, the server is able to start, but shows this error upon startup:
{code}
Unable to retrieve a list of remote deployment scanners for server WildFly 10.x
org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote://localhost:9999. The connection timed out
at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:361)
at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.execute(Wildfly9ManagerService.java:171)
at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:295)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility$1.execute(AS7DeploymentScannerUtility.java:1)
at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerUtil.executeWithService(JBoss7ManagerUtil.java:136)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.executeWithResult(AS7DeploymentScannerUtility.java:293)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScanners(AS7DeploymentScannerUtility.java:164)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScannersBlocking(AS7DeploymentScannerUtility.java:124)
at org.jboss.ide.eclipse.as.core.server.internal.v7.AS7DeploymentScannerUtility.getDeploymentScannersBlocking(AS7DeploymentScannerUtility.java:114)
at org.jboss.ide.eclipse.as.ui.dialogs.ModifyDeploymentScannerIntervalDialog$DeploymentScannerUIServerStartedListener$1.run(ModifyDeploymentScannerIntervalDialog.java:82)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote://localhost:9999. The connection timed out
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.execute(Wildfly9Manager.java:350)
... 11 more
Caused by: java.net.ConnectException: WFLYPRT0023: Could not connect to remote://localhost:9999. The connection timed out
at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:124)
at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:257)
at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:71)
at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:212)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:147)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:122)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
... 13 more
{code}
The server seems to be started alright:
{code}
12:47:43,771 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9999/management
12:47:43,771 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9999
12:47:43,772 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.1.0.Final (WildFly Core 2.2.0.Final) started in 3670ms - Started 405 of 655 services (404 services are lazy, passive or on-demand)
{code}
And then when I try to stop the server, it fails also:
Server WildFly 10.x failed to stop.
{code}
Could not stop server adapter WildFly 10.x
org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote://localhost:9999. The connection timed out
at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.quietlyExecute(Wildfly9Manager.java:373)
at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.stopServer(Wildfly9Manager.java:284)
at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9ManagerService.stop(Wildfly9ManagerService.java:162)
at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.stop(JBoss7ManagerServiceProxy.java:83)
at org.jboss.tools.as.core.server.controllable.subsystems.internal.ManagementShutdownController.gracefullStop(ManagementShutdownController.java:81)
at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stopImpl(LocalLegacyShutdownController.java:129)
at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:66)
at org.jboss.tools.as.core.server.controllable.subsystems.internal.LocalLegacyShutdownController.stop(LocalLegacyShutdownController.java:53)
at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.stop(ControllableServerBehavior.java:255)
at org.eclipse.wst.server.core.internal.Server.stopImpl2(Server.java:3688)
at org.eclipse.wst.server.core.internal.Server.stopImpl(Server.java:3645)
at org.eclipse.wst.server.core.internal.Server$StopJob.run(Server.java:403)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.io.IOException: java.net.ConnectException: WFLYPRT0023: Could not connect to remote://localhost:9999. The connection timed out
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:75)
at org.jboss.ide.eclipse.as.internal.management.wildfly9.Wildfly9Manager.quietlyExecute(Wildfly9Manager.java:368)
... 12 more
Caused by: java.net.ConnectException: WFLYPRT0023: Could not connect to remote://localhost:9999. The connection timed out
at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:124)
at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:257)
at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:71)
at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:212)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:147)
at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:122)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
... 14 more
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24232) New application wizard: NPE when trying to inspect defined resources for jenkins-pipeline-example
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24232?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24232:
------------------------------------------
This depends on added support for the build startegy type JenkinsPipeline in the client library: https://github.com/openshift/openshift-restclient-java/issues/268
> New application wizard: NPE when trying to inspect defined resources for jenkins-pipeline-example
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24232
> URL: https://issues.jboss.org/browse/JBIDE-24232
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3, pipeline_build
> Fix For: 4.4.4.AM3
>
> Attachments: pipeline-buildconfig-entry.png
>
>
> steps:
> # ASSERT: use a cdk which has the "jenkins-pipeline-example" template
> # EXEC: launch the app wizard and in the list of available server templates select the "jenkins-pipeline-example" template
> # ASSERT: Details panel shows the details for this template and holds a button "Defined Resources..."
> # EXEC: hit the "Defined Resources..." button
> # ASSERT: Details dialog pops up listing all the resources
> # EXEC: click the 2nd build config "BuildConfig {sample-pipeline}"
> !pipeline-buildconfig-entry.png!
> Result:
> arrow (or +) to the left of the build config disappears, nothing else happens. In the Eclipse log you discover an NPE:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ResourceDetailsContentProvider.getBuildConfigChildren(ResourceDetailsContentProvider.java:93)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ResourceDetailsContentProvider.getChildren(ResourceDetailsContentProvider.java:49)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1372)
> at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:341)
> at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:907)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:621)
> at org.eclipse.jface.viewers.AbstractTreeViewer.lambda$0(AbstractTreeViewer.java:817)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:795)
> at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:596)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:766)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1493)
> at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:882)
> at org.eclipse.jface.viewers.AbstractTreeViewer$3.treeExpanded(AbstractTreeViewer.java:1505)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:133)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
> at org.eclipse.swt.widgets.TreeItem.sendExpand(TreeItem.java:1050)
> at org.eclipse.swt.widgets.Tree.expandItem_expandChildren(Tree.java:1278)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5996)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227)
> at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1135)
> at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2102)
> at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1127)
> at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2624)
> at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2069)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5733)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227)
> at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2140)
> at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2402)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5797)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5226)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5375)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3703)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceListPage$13.widgetSelected(ApplicationSourceListPage.java:590)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4080)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3706)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270)
> at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:433)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:454)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:482)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4080)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3706)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24232) New application wizard: NPE when trying to inspect defined resources for jenkins-pipeline-example
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24232?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24232:
-------------------------------------
Attachment: (was: image-2017-04-06-12-04-15-876.png)
> New application wizard: NPE when trying to inspect defined resources for jenkins-pipeline-example
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24232
> URL: https://issues.jboss.org/browse/JBIDE-24232
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3, pipeline_build
> Fix For: 4.4.4.AM3
>
> Attachments: pipeline-buildconfig-entry.png
>
>
> steps:
> # ASSERT: use a cdk which has the "jenkins-pipeline-example" template
> # EXEC: launch the app wizard and in the list of available server templates select the "jenkins-pipeline-example" template
> # ASSERT: Details panel shows the details for this template and holds a button "Defined Resources..."
> # EXEC: hit the "Defined Resources..." button
> # ASSERT: Details dialog pops up listing all the resources
> # EXEC: click the 2nd build config "BuildConfig {sample-pipeline}"
> !pipeline-buildconfig-entry.png!
> Result:
> arrow (or +) to the left of the build config disappears, nothing else happens. In the Eclipse log you discover an NPE:
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ResourceDetailsContentProvider.getBuildConfigChildren(ResourceDetailsContentProvider.java:93)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ResourceDetailsContentProvider.getChildren(ResourceDetailsContentProvider.java:49)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1372)
> at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:341)
> at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:907)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:621)
> at org.eclipse.jface.viewers.AbstractTreeViewer.lambda$0(AbstractTreeViewer.java:817)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:795)
> at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:596)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:766)
> at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1493)
> at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:882)
> at org.eclipse.jface.viewers.AbstractTreeViewer$3.treeExpanded(AbstractTreeViewer.java:1505)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:133)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
> at org.eclipse.swt.widgets.TreeItem.sendExpand(TreeItem.java:1050)
> at org.eclipse.swt.widgets.Tree.expandItem_expandChildren(Tree.java:1278)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5996)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227)
> at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1135)
> at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2102)
> at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1127)
> at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2624)
> at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2069)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5733)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227)
> at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2140)
> at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2402)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5797)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5226)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5375)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3703)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceListPage$13.widgetSelected(ApplicationSourceListPage.java:590)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4080)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3706)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270)
> at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:433)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:454)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:482)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4256)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1313)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4080)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3706)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> 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:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years