[JBoss JIRA] (JBIDE-16600) Unhandled event loop exception after some time
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16600?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-16600 at 2/17/14 10:45 AM:
-----------------------------------------------------------------
Pavol Srna confirmed he has seen this and he, too, has no clue as to what causes this.
Now, when I stopped the remote EAP 6.2 in my workspace, I got 2 more of these errors in the error view. Then I stopped a local EAP 6.2 instance, but that didn't show errors.
was (Author: mmalina):
Pavol Srna confirmed he has seen this and he, too, has no clue as to what causes this.
> 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
12 years, 2 months
[JBoss JIRA] (JBIDE-14744) Allow users to choose from quickstarts/templates when creatingApplication wizard: new application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14744?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14744:
------------------------------------------
It turns out that the spec is incomplete when it comes to cartridges:
{quote}
a) a comma delimited list of cartridge name search conditions
b) a string containing a JSON array
{quote}
It is currently as follows:
# comma delimited list of SPEC
# json arry of any valid json that one can send to the broker
SPEC :=
* name-pattern
* url
> Allow users to choose from quickstarts/templates when creatingApplication wizard: new application
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14744
> URL: https://issues.jboss.org/browse/JBIDE-14744
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.1.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.2.0.Beta1
>
> Attachments: 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.png, alternative-cartridges.png, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.png, openshift-quickstart.png
>
>
> The web ui offers a large set of quickstarts/templates:
> !openshift-quickstart.png!
> in a mail from clayton on the 4th of june:
> {quote}
> For QuickStarts, brokers may choose to
> a) enable community quickstarts
> (the URL you saw below, set by COMMUNITY_QUICKSTART_URL being a URL in /etc/openshift/broker.conf)
> b) enable their own list of quickstarts
> (a different url, /broker/rest/quickstarts, configured from /etc/openshift/quickstarts.json)
> c) disable the quickstarts link
> (delete /etc/openshift/quickstarts.json)
> To correctly fetch the quickstarts for a server, retrieve the API document
> /broker/rest/api
> and look for the LIST_QUICKSTARTS link. If it is present, you may retrieve quickstarts. If it is absent, you should assume there are no quickstarts.
> Retrieving the list of quickstarts, unlike other REST API feed calls, is very specific:
> * API versioning is not supported
> * Only JSON is supported
> * The body of the response is slightly different than standard REST API feed results
> * If you encounter a parse error or an unexpected data value you are required to handle it gracefully by omitting the entry - the API may change without warning (although hopefully not)
> The format of the JSON response (in either a) or b) above) is:
> {quote}
> {code}
> {
> data: [
> quickstart: {
> id: "<string id>",
> href: "<absolute URL to a display URL for the quickstart>",
> name: "<name>",
> updated: "<last update date in seconds from the epoch>",
> summary: "<brief HTML body of the item>",
> body: "<full HTML body of the item>",
> cartridges: "<cartridge spec>",
> website: "<URL of metadata about the source of the quickstart or the technology>",
> tags: "<comma delimited list of tags>",
> language: "<display name of the type of quickstart>",
> initial_git_url: "<absolute URL or Git reference to source>",
> provider: "openshift|reviewed|partner|community", # default is community
> },
> ]
> }
> {code}
> {quote}
> You should assume that arbitrary content could be injected into any of these fields and defend yourself against XSS appropriately. You should also assume that the structure could be changed at any time.
> Cartridge spec:
> The cartridge spec is defined as either:
> a) a comma delimited list of cartridge name search conditions
> b) a string containing a JSON array
> If the leading character of the cartridge spec is '[', you must convert the cartridge spec to JSON and submit the value provided to the server on creation as the "cartridges" field.
> Otherwise,
> 1) split the string by "," into "segments"
> 2) trim whitespace from each segment
> 3) split each segment by "|" into "matches" - these represent logical ORs
> 4) strip leading and trailing "*" characters
> 5) For each segment, return all cartridges that have a case-insensitive substring match on any of the "matches" in that segment for the user to select.
> See https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea...
> and https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea...
> {quote}
--
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
12 years, 2 months
[JBoss JIRA] (JBIDE-16600) Unhandled event loop exception after some time
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16600?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-16600:
---------------------------------------
Pavol Srna confirmed he has seen this and he, too, has no clue as to what causes this.
> 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
12 years, 2 months
[JBoss JIRA] (JBIDE-16600) Unhandled event loop exception after some time
by 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
12 years, 2 months
[JBoss JIRA] (JBIDE-11919) Forge Console in JBDS/Tools - Screen "Garbage"
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11919?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-11919:
-----------------------------------
Could you attach (or describe in detail) the scripts you are executing? Or something that reproduces the issue?
> Forge Console in JBDS/Tools - Screen "Garbage"
> ----------------------------------------------
>
> Key: JBIDE-11919
> URL: https://issues.jboss.org/browse/JBIDE-11919
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 3.3.0.Beta3
> Environment: 3.3.Beta3 or JBDS5 Beta3
> Reporter: Burr Sutter
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 3.3.0.CR1
>
> Attachments: forgedemo.fsh, Screen Shot 2012-05-21 at 11.00.35 AM.png, Screen Shot 2012-05-21 at 11.05.15 AM.png, Screen Shot 2012-05-21 at 11.18.41 AM.png
>
>
> _____
> | ___|__ _ __ __ _ ___
> EC: echo echo CRN: /Users/burr/gettingstarted/workspaceToolsBeta2v3 CRT: DirectoryResource CPN: PAR: [Ljava.lang.String;@1371098d org.jboss.forge.shell.util.PipeOutImpl@622a11f3 EC: echo echo CRN: /Users/burr/gettingstarted/workspaceToolsBeta2v3 CRT: DirectoryResource CPN: PAR: [Ljava.lang.String;@38009ade org.jboss.forge.shell.util.PipeOutImpl@2fb7818b EC: echo echo CRN: /Users/burr/gettingstarted/workspaceToolsBeta2v3 CRT: DirectoryResource CPN: PAR: [Ljava.lang.String;@421dc8c8 org.jboss.forge.shell.util.PipeOutImpl@3004ed34
--
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
12 years, 2 months