Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 326235

Summary: After updating from 3.6 to 3.6 SR1 - Eclipse not starting workspace
Product: [Eclipse Project] Equinox Reporter: Paul <paulkuhn12>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: aniefer, irbull, pascal, remy.suen
Version: 3.6.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Paul CLA 2010-09-25 14:18:15 EDT 
Build Identifier: 3.6 SR1 (Helios)

I have updated the Helios 3.6 installation to 3.6 SR1 and restarted the workspace. However Eclipse did not start, after checking the log in the Eclipse configuration folder the following stack trace is shown.

!ENTRY org.eclipse.osgi 4 0 2010-09-25 20:12:34.049
!MESSAGE Application error
!STACK 1
java.lang.RuntimeException: Application "org.eclipse.ui.ide.workbench" could not be found in the registry. The applications available are: org.eclipse.ant.core.antRunner, org.eclipse.datatools.connectivity.console.profile.StorageFileEditor, org.eclipse.emf.importer.ecore.Ecore2GenModel, org.eclipse.emf.importer.java.Java2GenModel, org.eclipse.emf.importer.rose.Rose2GenModel, org.eclipse.equinox.p2.garbagecollector.application, org.eclipse.equinox.p2.metadata.generator.EclipseGenerator, org.eclipse.equinox.p2.reconciler.application, org.eclipse.pde.junit.runtime.uitestapplication, org.eclipse.pde.junit.runtime.legacytestapplication, org.eclipse.pde.junit.runtime.coretestapplication, org.eclipse.pde.junit.runtime.coretestapplicationnonmain, org.eclipse.pde.junit.runtime.nonuithreadtestapplication, org.eclipse.wst.server.preview.preview, org.eclipse.emf.codegen.CodeGen, org.eclipse.emf.codegen.JMerger, org.eclipse.emf.codegen.ecore.Generator, org.eclipse.equinox.app.error, org.eclipse.equinox.p2.director.app.application, org.eclipse.equinox.p2.director, org.eclipse.equinox.p2.publisher.InstallPublisher, org.eclipse.equinox.p2.publisher.EclipseGenerator, org.eclipse.equinox.p2.publisher.ProductPublisher, org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher, org.eclipse.equinox.p2.repository.repo2runnable, org.eclipse.equinox.p2.repository.metadataverifier, org.eclipse.equinox.p2.artifact.repository.mirrorApplication, org.eclipse.equinox.p2.metadata.repository.mirrorApplication, org.eclipse.equinox.p2.updatesite.UpdateSitePublisher, org.eclipse.equinox.p2.publisher.UpdateSitePublisher, org.eclipse.equinox.p2.publisher.CategoryPublisher, org.eclipse.help.base.infocenterApplication, org.eclipse.help.base.helpApplication, org.eclipse.help.base.indexTool, org.eclipse.jdt.apt.core.aptBuild, org.eclipse.jdt.core.JavaCodeFormatter, org.eclipse.pde.build.Build, org.eclipse.update.core.standaloneUpdate, org.eclipse.update.core.siteOptimizer, org.eclipse.wst.jsdt.core.JavaCodeFormatter.
	at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:248)
	at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29)
	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:369)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1383)


Not sure what causes this, I was expecting that a minor update does not corrupt the workspace.

Thanks.
Paul


Reproducible: Always
Comment 1 Paul CLA 2010-09-25 14:25:49 EDT 
By the way. The select workspace dialog is not even shown. An error dialog "An error has occured" comes right away after starting Helios. This happened right after I have run the updater to SR1...
Comment 2 John Arthorne CLA 2010-09-27 10:33:04 EDT 
What Helios package did you have installed - Java EE, Modeling, etc?

How did you upgrade? Did you upgrade via Help > Check for Updates, or a manual install of SR1?
Comment 3 Andrew Niefer CLA 2010-09-27 11:01:02 EDT 
This kind of error occurs before choosing the workspace, if it is any consolation, the workspace should be fine.
This is a configuration problem with Eclipse itself, it seems that you may be missing some plug-ins in the install.

Is "org.eclipse.ui.ide.application" listed in eclipse/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info ?
Comment 4 Paul CLA 2010-09-28 03:28:57 EDT 
I did have installed Java EE 3.6.0 and upgraded via Help > Check for Updates.
Comment 5 Paul CLA 2010-09-28 03:32:34 EDT 
I have realized that the upgraded Eclipse runs fine if I create a new, fresh workspace. I forgot to mention that I am using the 64-bit version of Eclipse.

By further investigation I suspect that the Subversive Plugin from Polarion caused this issue. It was installed on Helios 3.6.0. Now running 3.6.1 in a brand-new workspace, I can not install it anymore.
Comment 6 John Arthorne CLA 2010-09-28 09:09:39 EDT 
(In reply to comment #5)
> I have realized that the upgraded Eclipse runs fine if I create a new, fresh
> workspace. I forgot to mention that I am using the 64-bit version of Eclipse.
> 
> By further investigation I suspect that the Subversive Plugin from Polarion
> caused this issue. It was installed on Helios 3.6.0. Now running 3.6.1 in a
> brand-new workspace, I can not install it anymore.

If the Subversive plugin is incompatible with 3.6.1, the installer shouldn't have attempted an upgrade that would break the install.

I see you are on Windows 7. By any chance did you have Eclipse installed somewhere under C:\Program Files? This triggers a shared install mode in Eclipse that behaves a bit differently.
Comment 7 Paul CLA 2010-09-29 09:08:50 EDT 
(In reply to comment #6)

No Eclipse has been installed in a different folder than c:\Program Files.
Comment 8 Pascal Rapicault CLA 2011-06-11 23:54:43 EDT 
I have not been able to reproduce this.