Eclipse Community Forums: Eclipse Platform » Eclipse won't start after computer crash and -clean option

Home » Eclipse Projects » Eclipse Platform » Eclipse won't start after computer crash and -clean option

Eclipse won't start after computer crash and -clean option [message #333888]

Mon, 12 January 2009 12:35

Eclipse User

Hi:

I was forced to do a hard shutdown of my computer over the weekend while
(I believe) Eclipse was running. This morning, I've tried to start
Eclipse and it seems to continually restart while only showing the splash
screen. The error log looks like:

!SESSION 2009-01-12 09:10:03.578
-----------------------------------------------
eclipse.buildId=M20080911-1700
java.version=1.5.0_16
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86

!ENTRY org.eclipse.osgi 4 0 2009-01-12 09:10:10.765
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: Cannot attach fragment bundle
"org.eclipse.equinox.weaving.hook" to resolved host "org.eclipse.osgi".
Try refreshing the host bundle.
at
org.eclipse.osgi.framework.internal.core.BundleHost.attachFr agment(BundleHost.java:575)
at
org.eclipse.osgi.framework.internal.core.BundleFragment.addH ost(BundleFragment.java:298)
at
org.eclipse.osgi.framework.internal.core.PackageAdminImpl.se tResolved(PackageAdminImpl.java:336)
at
org.eclipse.osgi.framework.internal.core.PackageAdminImpl.se tResolvedBundles(PackageAdminImpl.java:602)
at
org.eclipse.osgi.framework.internal.core.SystemBundleActivat or.start(SystemBundleActivator.java:59)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:1009)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tartActivator(BundleContextImpl.java:1003)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tart(BundleContextImpl.java:984)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:280)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:489)
at
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:211)
at
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:321)

!ENTRY org.eclipse.osgi 4 0 2009-01-12 09:10:10.781
!MESSAGE Bundle
initial@reference :file:plugins/org.eclipse.equinox.simpleconfigurator_1.0.0.v 20080604.jar/
[1] is not active.

I've searched and searched and tried starting Eclipse with the -clean
option. In this case, Eclipse does not continue to reboot but it still
never makes it past the splash screen. The error now is:
!SESSION 2009-01-12 10:22:22.250
-----------------------------------------------
eclipse.buildId=M20080911-1700
java.version=1.6.0_07
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -clean

!ENTRY org.eclipse.equinox.simpleconfigurator 4 0 2009-01-12 10:22:26.171
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: Exception in
org.eclipse.equinox.internal.simpleconfigurator.Activator.st art() of
bundle org.eclipse.equinox.simpleconfigurator.
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tartActivator(BundleContextImpl.java:1028)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tart(BundleContextImpl.java:984)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:346)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:355)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1074)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:616)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:508)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:299)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.l aunch(StartLevelManager.java:247)
at
org.eclipse.osgi.framework.internal.core.SystemBundle.resume (SystemBundle.java:201)
at
org.eclipse.osgi.framework.internal.core.Framework.launch(Fr amework.java:644)
at org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.ja va:51)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.startup(Ecli pseStarter.java:313)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
Caused by: java.lang.IllegalStateException: The state indicates the bundle
is resolved
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolutionFailureMessage(AbstractBundle.java:1381)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:305)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.star t(AbstractBundle.java:265)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.star t(AbstractBundle.java:257)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplie r.startBundles(ConfigApplier.java:317)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplie r.install(ConfigApplier.java:86)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfig uratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:12 4)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfig uratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:13 8)
at
org.eclipse.equinox.internal.simpleconfigurator.Activator.st art(Activator.java:48)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:1009)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tartActivator(BundleContextImpl.java:1003)
... 21 more
Root exception:
java.lang.IllegalStateException: The state indicates the bundle is resolved
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.getR esolutionFailureMessage(AbstractBundle.java:1381)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:305)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.star t(AbstractBundle.java:265)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.star t(AbstractBundle.java:257)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplie r.startBundles(ConfigApplier.java:317)
at
org.eclipse.equinox.internal.simpleconfigurator.ConfigApplie r.install(ConfigApplier.java:86)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfig uratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:12 4)
at
org.eclipse.equinox.internal.simpleconfigurator.SimpleConfig uratorImpl.applyConfiguration(SimpleConfiguratorImpl.java:13 8)
at
org.eclipse.equinox.internal.simpleconfigurator.Activator.st art(Activator.java:48)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:1009)
at java.security.AccessController.doPrivileged(Native Method)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tartActivator(BundleContextImpl.java:1003)
at
org.eclipse.osgi.framework.internal.core.BundleContextImpl.s tart(BundleContextImpl.java:984)
at
org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:346)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:355)
at
org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1074)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:616)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:508)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:299)
at
org.eclipse.osgi.framework.internal.core.StartLevelManager.l aunch(StartLevelManager.java:247)
at
org.eclipse.osgi.framework.internal.core.SystemBundle.resume (SystemBundle.java:201)
at
org.eclipse.osgi.framework.internal.core.Framework.launch(Fr amework.java:644)
at org.eclipse.osgi.framework.internal.core.OSGi.launch(OSGi.ja va:51)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.startup(Ecli pseStarter.java:313)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:175)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)

!ENTRY org.eclipse.osgi 4 0 2009-01-12 10:22:27.500
!MESSAGE Bundle
initial@reference :file:plugins/org.eclipse.equinox.simpleconfigurator_1.0.0.v 20080604.jar/
[3] is not active.

Any help would be greatly appreciated

Re: Eclipse won't start after computer crash and -clean option [message #333891 is a reply to message #333888]

Mon, 12 January 2009 14:58

Eclipse User

Also this is my config.ini if that helps:

#This configuration file was written by:
org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxF wConfigFileParser
#Mon Jan 05 11:24:29 MST 2009
osgi.launcherPath=.
org.eclipse.update.reconcile=false
eclipse.p2.profile=PlatformProfile
osgi.instance.area.default=@user.home/workspace
osgi.framework=file\:plugins\\org.eclipse.osgi_3.4.2.R34x_v2 0080826-1230.jar
eclipse.buildId=M20080911-1700
org.aspectj.osgi.verbose=true
org.aspectj.weaver.showWeaveInfo=true
osgi.bundles=reference\:file\:org.eclipse.equinox.weaving.hook_1.0.0.200812180852.jar@4,reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar@1\:start
org.eclipse.equinox.simpleconfigurator.configUrl=file\:org.e clipse.equinox.simpleconfigurator\\bundles.info
aj.weaving.verbose=true
eclipse.product=org.eclipse.platform.ide
osgi.splashPath=platform\:/base/plugins/org.eclipse.platform
osgi.launcherIni=eclipse
osgi.framework.extensions=org.eclipse.equinox.weaving.hook
eclipse.p2.data.area=@config.dir/../p2
osgi.bundles.defaultStartLevel=4

Re: Eclipse won't start after computer crash and -clean option [message #333892 is a reply to message #333891]

Mon, 12 January 2009 15:32

Eclipse User

Update:

Seems that if i comment out all references to org.eclipse.equinox.weaving
in config.ini that Eclipse actually boots up. Not sure what that will
affect, but I'm going to go ahead and try to uninstall/reinstall AJDT and
SpringIDE/DM features as I know they use aspect things (assuming the
weaving bits have to do w/ aspects).

Still, leaves me with an uncomfortable feeling, so if anyone has a clue
how to better fix this or insight into what is going on, that would be
much appreciated!

Re: Eclipse won't start after computer crash and -clean option [message #333893 is a reply to message #333892]

Tue, 13 January 2009 02:04

Eclipse User

"Andrew Ochsner" <aochsner@cs.stanford.edu> wrote in message
news:a7b9583b6277540c328d1c5933afd831$1@www.eclipse.org...
> Update:
>
> Seems that if i comment out all references to org.eclipse.equinox.weaving
> in config.ini that Eclipse actually boots up. Not sure what that will
> affect, but I'm going to go ahead and try to uninstall/reinstall AJDT and
> SpringIDE/DM features as I know they use aspect things (assuming the
> weaving bits have to do w/ aspects).
>
> Still, leaves me with an uncomfortable feeling, so if anyone has a clue
> how to better fix this or insight into what is going on, that would be
> much appreciated!

I think at that point I'd probably just download and install Eclipse
again...

Re: Eclipse won't start after computer crash and -clean option [message #333896 is a reply to message #333892]

Tue, 13 January 2009 04:30

Eclipse User

On Mon, 12 Jan 2009 20:32:27 +0000 (UTC), aochsner@cs.stanford.edu
(Andrew Ochsner) wrote:

> ...
>
>Still, leaves me with an uncomfortable feeling, so if anyone has a clue
>how to better fix this or insight into what is going on, that would be
>much appreciated!

From experience during the last days updating a system with p2 it
might help to delete the configuration area (usually
$HOME/.eclipse/<version-specific-dir> or
%APPDATA%\<version-specific-dir>).

Achim
--
Achim Lörke

Eclipse-Stammtisch in the Braunschweig, Germany area:
http://www.bredex.de/de/news/events.html

Re: Eclipse won't start after computer crash and -clean option [message #333902 is a reply to message #333896]

Tue, 13 January 2009 10:30

Eclipse User

I've looked around but I'm not sure I have a <version-specific-dir> under
%APPDATA%. So far, seems that removing the org.eclipse.equinox.weaving
and the AJDT plugins as well as the plugins that refer to AJDT and
reinstalling them has at least made things work again.

Whats an example of this directory you're talking about? First I've heard
of it.

Re: Eclipse won't start after computer crash and -clean option [message #333923 is a reply to message #333902]

Wed, 14 January 2009 04:13

Eclipse User

On Tue, 13 Jan 2009 15:30:14 +0000 (UTC), aochsner@cs.stanford.edu
(Andrew Ochsner) wrote:

>I've looked around but I'm not sure I have a <version-specific-dir> under
>%APPDATA%. So far, seems that removing the org.eclipse.equinox.weaving
>and the AJDT plugins as well as the plugins that refer to AJDT and
>reinstalling them has at least made things work again.
>
>Whats an example of this directory you're talking about? First I've heard
>of it.

I meant the directory you can specify using the -configuration command
line option or by setting the "osgi.configuration.area" variable. It
contains bundle descriptions and several not workspace related
settings. Since we use an shared installation on a Windows 2008
Terminal Server this directory is in %APPDATA% or in the users "local
home" which is "C:\Users\<userid>" on our server (if I remember right
this can be configured by the server admin). The default locations are
documented in the Eclipse Help for the "osgi.configuration.area"
variable.

If this directory constains invalid data it will not be cleared by the
"-clean" option. The only way to get a clean base is removing the
directory.

Achim
--
Achim Lörke

Eclipse-Stammtisch in the Braunschweig, Germany area:
http://www.bredex.de/de/news/events.html

Previous Topic:	Object contribution and Project Explorer
Next Topic:	CVS 'Pretent to be a Unix CVS version' needed for Eclipse 3.4.1?

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Oct 30 21:22:28 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter