Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Oomph » Error "unknown protocol: archive"
Error "unknown protocol: archive" [message #1850285] Wed, 23 February 2022 21:35 Go to next message
Lutz Wrage is currently offline Lutz WrageFriend
Messages: 181
Registered: July 2009
Senior Member
I just encountered a strange situation: I use the eclipse installer to install eclipse 2021-03 and add a setup to install a bunch of plugins, and clone and import a github project. This has worked perfectly for years until last week. Today index:/org.eclipse setup can no longer be resolved. There is an error "org.eclipse.oomph.util.IOExceptionWithCause: unknown protocol: archive: archive:http://www.eclipse.org/setups/setups.zip!/http/git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/org.eclipse.setup" on the entry in the user.setup.
Any idea what may be wrong? AFAICT, the only thing that changed since last week is that I updated the installer to the latest version that has the new trust settings (and complains about some expired or unknown certificates).
Re: Error "unknown protocol: archive" [message #1850289 is a reply to message #1850285] Thu, 24 February 2022 07:35 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 33254
Registered: July 2009
Senior Member
Could you show the complete stack trace of this exception? The archive scheme is supported directly by EMF so I don't expect such a failure. Is this happening in the installer or the installed IDE?

Ed Merks
Professional Support: https://www.macromodeling.com/
Re: Error "unknown protocol: archive" [message #1850297 is a reply to message #1850289] Thu, 24 February 2022 13:05 Go to previous messageGo to next message
Lutz Wrage is currently offline Lutz WrageFriend
Messages: 181
Registered: July 2009
Senior Member
Some more detail: Eclipse installs, and starts, but then in the installed eclipse no setup tasks, e.g., clone git repo, targlets, etc., are executed.
When I open the user setup the second node shown is "index:/org.eclipse.setup" with an error marker. The error is the unknown protocol.
The last entry in the setup log is "Launching the installed product..."
The setup file is https://raw.githubusercontent.com/osate/osate2/master/setup/osate2_2021-03.setup
The stack trace in the error log is
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.eclipse.oomph.util.IOExceptionWithCause: unknown protocol: archive: archive:http://www.eclipse.org/setups/setups.zip!/http/git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/org.eclipse.setup
	at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.handleDemandLoadException(ResourceSetImpl.java:319)
	at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:278)
	at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$ResourceLocator.demandLoadHelper(ResourceSetImpl.java:804)
	at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$MappedResourceLocator.getResource(ResourceSetImpl.java:1204)
	at org.eclipse.oomph.setup.internal.core.util.SetupCoreUtil$3.getResource(SetupCoreUtil.java:466)
	at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:352)
	at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getEObject(ResourceSetImpl.java:220)
	at org.eclipse.emf.ecore.util.EcoreUtil.resolve(EcoreUtil.java:209)
	at org.eclipse.emf.ecore.util.EcoreUtil.resolve(EcoreUtil.java:269)
	at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eResolveProxy(BasicEObjectImpl.java:1516)
	at org.eclipse.oomph.setup.impl.InstallationImpl.getProductVersion(InstallationImpl.java:79)
	at org.eclipse.oomph.setup.internal.core.SetupContext.getInstallation(SetupContext.java:669)
	at org.eclipse.oomph.setup.internal.core.SetupContext.create(SetupContext.java:281)
	at org.eclipse.oomph.setup.ui.wizards.SetupWizard.<init>(SetupWizard.java:186)
	at org.eclipse.oomph.setup.ui.wizards.SetupWizard.<init>(SetupWizard.java:174)
	at org.eclipse.oomph.setup.ui.wizards.SetupWizard$Updater.<init>(SetupWizard.java:1746)
	at org.eclipse.oomph.setup.ui.wizards.SetupWizard$Updater$1.<init>(SetupWizard.java:1792)
	at org.eclipse.oomph.setup.ui.wizards.SetupWizard$Updater.perform(SetupWizard.java:1792)
	at org.eclipse.oomph.setup.presentation.handlers.PerformHandler.run(PerformHandler.java:51)
	at org.eclipse.oomph.setup.presentation.handlers.AbstractDropdownItemHandler.execute(AbstractDropdownItemHandler.java:50)
	at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:283)
	at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:97)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:319)
	at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:253)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:173)
	at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:156)
	at org.eclipse.core.commands.Command.executeWithChecks(Command.java:488)
	at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:487)
	at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
	at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:438)
	at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449)
	at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:475)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5831)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1427)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:5092)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4570)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1157)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1046)
	at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
	at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:551)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:156)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
	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:401)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1461)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1434)
Caused by: org.eclipse.oomph.util.IOExceptionWithCause: unknown protocol: archive: archive:http://www.eclipse.org/setups/setups.zip!/http/git.eclipse.org/c/oomph/org.eclipse.oomph.git/plain/setups/org.eclipse.setup
	at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl.createIOException(ECFURIHandlerImpl.java:555)
	at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl.access$15(ECFURIHandlerImpl.java:542)
	at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl$ConnectionHandler.process(ECFURIHandlerImpl.java:1805)
	at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl.createInputStream(ECFURIHandlerImpl.java:323)
	at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.createInputStream(ExtensibleURIConverterImpl.java:358)
	at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1314)
	at org.eclipse.oomph.setup.internal.core.util.ResourceMirror$LoadJob.perform(ResourceMirror.java:232)
	at org.eclipse.oomph.util.WorkerPool$Worker.run(WorkerPool.java:437)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: java.net.MalformedURLException: unknown protocol: archive
	at java.base/java.net.URL.<init>(URL.java:652)
	at java.base/java.net.URL.fromURI(URL.java:719)
	at java.base/java.net.URI.toURL(URI.java:1116)
	at org.eclipse.ecf.provider.filetransfer.identity.FileTransferID.getURL(FileTransferID.java:80)
	at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:879)
	at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:578)
	at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:108)
	at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl$InputStreamConnectionHandler.sendConnectionRequest(ECFURIHandlerImpl.java:1950)
	at org.eclipse.oomph.setup.internal.core.util.ECFURIHandlerImpl$ConnectionHandler.process(ECFURIHandlerImpl.java:1649)
	... 6 more
Re: Error "unknown protocol: archive" [message #1850301 is a reply to message #1850297] Thu, 24 February 2022 13:35 Go to previous messageGo to next message
Lutz Wrage is currently offline Lutz WrageFriend
Messages: 181
Registered: July 2009
Senior Member
Oh, and this is on Kubuntu 21.10 with the 11.0.14 JVM from the installer.
Re: Error "unknown protocol: archive" [message #1850304 is a reply to message #1850301] Thu, 24 February 2022 15:39 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 33254
Registered: July 2009
Senior Member
Does the IDE you have installed include CDO, e.g., is it in modeling package? I know that CDO messed with the URI handlers and caused this type of problem. I worked around it with newer versions of Oomph, but what's different now is that the latest version of Oomph cannot be installed in order versions of the platform, so the version on the release train will be used, and if it's an old release it's quite an old version of Oomph. So one workaround would be to include the URL for https://download.eclipse.org/oomph/updates/release/ (really big and slow to load) or https://download.eclipse.org/oomph/drops/release/1.23.0/ (small in installs in quite old versions of Eclipse).

Ed Merks
Professional Support: https://www.macromodeling.com/
Re: Error "unknown protocol: archive" [message #1850311 is a reply to message #1850304] Thu, 24 February 2022 19:42 Go to previous messageGo to next message
Lutz Wrage is currently offline Lutz WrageFriend
Messages: 181
Registered: July 2009
Senior Member
Thank you Ed, that fixed it! I'm still a bit puzzled by the fact that it worked until last week, though.
Re: Error "unknown protocol: archive" [message #1850323 is a reply to message #1850311] Fri, 25 February 2022 06:02 Go to previous messageGo to next message
Ed Merks is currently offline Ed MerksFriend
Messages: 33254
Registered: July 2009
Senior Member
By default the installers include https://download.eclipse.org/oomph/updates/milestone/latest so as soon as I built a new milestone for 2022-03 M3 this week, that site contained a version of Oomph where the p2 infrastructure has a lower bound satisfied only by the latest 4.23 p2 bundles of the platform. So basically most of the latest Oomph parts will not be installed into older products. I've been trying to keep everything backward compatible, but in this case the changes to accommodate PGP signing in p2 were too invasive and I generalized p2 itself to do a better job on its own to remember certificates and keys, eliminating the need for so much specialized hacking in Oomph. Note that the release train repos contains the version of Oomph that was available for that release and that will be installed instead for older products.

Ed Merks
Professional Support: https://www.macromodeling.com/
Re: Error "unknown protocol: archive" [message #1850335 is a reply to message #1850323] Fri, 25 February 2022 12:37 Go to previous message
Lutz Wrage is currently offline Lutz WrageFriend
Messages: 181
Registered: July 2009
Senior Member
Thanks a lot for the detailed explanation!
Previous Topic:Product partial update on latest product version
Next Topic:Error: An internal error occurred during: "Exporting Eclipse Profile"
Goto Forum:
  


Current Time: Thu Nov 14 04:39:22 GMT 2024

Powered by FUDForum. Page generated in 0.03105 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top