[jbosstools-issues] [JBoss JIRA] (JBIDE-16600) Unhandled event loop exception after some time

[Martin Malina (JIRA)]

Martin Malina created JBIDE-16600:
-------------------------------------

             Summary: Unhandled event loop exception after some time
                 Key: JBIDE-16600
                 URL: https://issues.jboss.org/browse/JBIDE-16600
             Project: Tools (JBoss Tools)
          Issue Type: Bug
    Affects Versions: 4.2.0.Alpha2
         Environment: JBDS 8.0.0.Alpha2b B71
            Reporter: Martin Malina
             Fix For: 4.2.0.Beta1


Got this:
Unhandled event loop exception
{code}
org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed)
	at org.eclipse.swt.SWT.error(SWT.java:4441)
	at org.eclipse.swt.SWT.error(SWT.java:4356)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3978)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
	at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
Caused by: org.eclipse.swt.SWTException: Widget is disposed
	at org.eclipse.swt.SWT.error(SWT.java:4441)
	at org.eclipse.swt.SWT.error(SWT.java:4356)
	at org.eclipse.swt.SWT.error(SWT.java:4327)
	at org.eclipse.swt.widgets.Widget.error(Widget.java:783)
	at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:573)
	at org.eclipse.swt.widgets.Control.setEnabled(Control.java:3711)
	at org.jboss.ide.eclipse.as.ui.editor.internal.StandardDeploymentPageController.updateWidgetEnablement(StandardDeploymentPageController.java:114)
	at org.jboss.ide.eclipse.as.ui.editor.internal.StandardDeploymentPageController$1$1.run(StandardDeploymentPageController.java:98)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
	... 23 more
{code}

Unfortunately I don't have much information here. I don't know what triggers this. It happened today when I verified some JIRAs in JBDS. I have AS 5.1, WildFly 8, EAP 6.2 and another remote EAP 6.2 set up in the workspace. Only one project - Java EE Web project from Central. 

I started the different servers, deployed, undeployed etc. And then did nothing for maybe 1 hour. When I came back to look at Eclipse, I saw there was this exception in the error log.

The thing is that this happened to me last week in different installation and different set of actions, but since it was too random, I didn't report a JIRA then. Now it's the second time, so I'm reporting a JIRA - perhaps somebody has seen the same?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira