Bugzilla – Full Text Bug Listing
| Summary: | Unhandled event loop exception while trying | ||
|---|---|---|---|
| Product: | [Modeling] Amalgam | Reporter: | Chris Min <chrismin1202> |
| Component: | UI | Assignee: | Project Inbox <amalgam.ui-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | cedric.brun, flexx, remy.suen |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
Chris Min
I can confirm this. Altough I don't get a time out, I can't even connect. I am behind a company firewall/proxy, however, I have no problems connecting to the Internet from Eclipse otherwise (e. g. updates, javadoc, etc.). Is there an issue with Amalgam not honoring the proxy settings, perhaps? It's also unfortunate that the error message does not give any indication as to which URL the connection attempt was made to. Thus there is no way to check if there actually _is_ some kind of connection problem to the discovery source. There may be a content filter in place on my firewall/proxy. However I doubt that. Thus I suggest catching java.net.ConnectException at org.eclipse.amalgam.discovery.modeling.handlers.ModelingDiscoveryHandler$1.load(ModelingDiscoveryHandler.java:63) and printing an error message including the URL tried to the error log as a first step to solve the issue. I had the problem in 4.3M4, and updating to 4.3M5 (just did it via p2, so I do have internet connectivity from eclipse!) didn't fix it. Here's my stack trace: org.eclipse.e4.core.di.InjectionException: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63) at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:231) at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:212) at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:131) at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:171) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:835) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:728) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:712) at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:647) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1057) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:941) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:79) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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: java.lang.RuntimeException: java.net.ConnectException: Connection refused: connect at org.eclipse.amalgam.discovery.modeling.handlers.ModelingDiscoveryHandler$1.load(ModelingDiscoveryHandler.java:63) at org.eclipse.amalgam.discovery.ui.viewer.DiscoveryContentProvider.getDiscovery(DiscoveryContentProvider.java:33) at org.eclipse.amalgam.discovery.ui.viewer.DiscoveryViewer.getDiscovery(DiscoveryViewer.java:1116) at org.eclipse.amalgam.discovery.ui.viewer.DiscoveryViewer.<init>(DiscoveryViewer.java:498) at org.eclipse.amalgam.discovery.ui.wizards.internal.DiscoveryWizardMainPage.createControl(DiscoveryWizardMainPage.java:56) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736) at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608) at org.eclipse.jface.window.Window.create(Window.java:431) at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104) at org.eclipse.jface.window.Window.open(Window.java:790) at org.eclipse.amalgam.discovery.modeling.handlers.ModelingDiscoveryHandler.execute(ModelingDiscoveryHandler.java:83) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) ... 33 more Caused by: java.net.ConnectException: Connection refused: connect at java.net.DualStackPlainSocketImpl.connect0(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source) at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source) at java.net.AbstractPlainSocketImpl.connect(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at sun.net.NetworkClient.doConnect(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.<init>(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at org.eclipse.emf.ecore.resource.impl.URIHandlerImpl.createInputStream(URIHandlerImpl.java:172) at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.createInputStream(ExtensibleURIConverterImpl.java:360) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1280) at org.eclipse.amalgam.discovery.modeling.handlers.ModelingDiscoveryHandler$1.load(ModelingDiscoveryHandler.java:58) ... 51 more Thanks for your effort! Thanks for your feedback. The file the discovery is trying to access is an XMI file stored on the eclipse http server. We are using EMF to load it. I assumed EMF was respecting the Eclipse proxy settings but based on your report it probably does not. I'll digg further. Here is an update site containing a first fix : https://hudson.eclipse.org/hudson/job/amalgam-1.2.0/275/artifact/features/org.eclipse.amalgam.update/target/org.eclipse.amalgam.update.zip I don't have a proxy myself so I had not really tested yet, feel free to have a try and tell me . I checked that defining a bogus proxy leads to the catalog not being resolved. This change will be part of the Kepler RC2 release, feel free to re-open if it is not fixing your problem. |