| The state indicates the bundle is resolved? [message #125672] |
Mon, 09 February 2009 10:05  |
Eclipse User |
|
|
|
Hi All,
I left Eclipse running over the weekend and my machine got rebooted. When
I tried to start it again this morning the Ganymede splash appeared and
then it seemed to hang. Nothing was written to the workspace log but I
found the information below in a timestamped log in the configuration
directory.
Can anyone tell me what has caused this issue? I had no option by to
reinstall.
TIA,
Miles
---
!SESSION 2009-02-09 09:02:45.816
-----------------------------------------------
eclipse.buildId=M20080911-1700
java.version=1.6.0_10
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Framework arguments: -refresh -plugincustomization
C:\dev\tools\eclipseide\3.4qa\eclipse\configuration\msde-glo bal-eclipse-prefs.ini
-showlocation
Command-line arguments: -os win32 -ws win32 -arch x86 -refresh -clean
-plugincustomization
C:\dev\tools\eclipseide\3.4qa\eclipse\configuration\msde-glo bal-eclipse-prefs.ini
-data C:\Documents and
Settings\radcliff\MSDE\eclipseide\3.4qa\workspaces\default -showlocation
!ENTRY org.eclipse.equinox.simpleconfigurator 4 0 2009-02-09 09:02:51.394
!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)
|
|
|
|
|
|
| Re: The state indicates the bundle is resolved? [message #126089 is a reply to message #125968] |
Fri, 20 February 2009 10:16  |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
On 2/19/2009 6:09 AM, Miles Daffin wrote:
> Hi Eric,
>
>> If this ever happens again, you can try running with the -clean
>> command line option to see if it will recover without requiring a
>> re-install.
>
> I always start eclipse with -clean. From the original message:
>
>>> ---
>>> !SESSION 2009-02-09 09:02:45.816
>>> -----------------------------------------------
>>> eclipse.buildId=M20080911-1700
>>> java.version=1.6.0_10
>>> java.vendor=Sun Microsystems Inc.
>>> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
>>> Framework arguments: -refresh -plugincustomization
>>> C:devtoolseclipseide3.4qaeclipseconfigurationmsde-global-ecl ipse-prefs.ini
>>>
>>> -showlocation
>>> Command-line arguments: -os win32 -ws win32 -arch x86 -refresh -clean
>>> -plugincustomization
>>> C:devtoolseclipseide3.4qaeclipseconfigurationmsde-global-ecl ipse-prefs.ini
>>>
>>> -data C:Documents and
>>> SettingsradcliffMSDEeclipseide3.4qaworkspacesdefault -showlocation
>
> This is happening to increasing numbers of users at my firm. They are
> all being forced to reinstall. Some people are having to reinstall once
> a week. This did not used to happen with 3.3.
>
> Any more ideas?
Other than to say that I've been using 3.4 for a year now, and the rest
of my team for several months and none of us has experienced a need to
re-install.
Of course Eclispe 3.4 is used by tens of thousands of people every day
for at least the past year. If Bugzilla doesn't have any related bugs
reported, I'd suggest that there might be something that everyone on
your team is doing similarly or some specific setup that causes problems
- I don't know.
Sorry, but this is not a widely reported issue (unless I've missed it in
my quick Bugzilla search).
<shrug>
Eric
|
|
|
|
|
| Re: The state indicates the bundle is resolved? [message #127180 is a reply to message #125747] |
Sat, 07 March 2009 18:33 |
| Eclipse User |
|
|
|
> Has anyone else seen this issue?
Just for the records: Yes, I remember seeing this error.
However, I gave up on reporting every p2 bug I observed,
I simply don't have the time to write all those reports...
So I don't have any details on when and where it happened.
sorry nothing to help spot the cause of this error,
Stephan
|
|
|
Powered by
FUDForum. Page generated in 0.04317 seconds
Home