Bug 272538 - OSGI kernel spits out exceptions at shutdown sometimes
Summary: OSGI kernel spits out exceptions at shutdown sometimes
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.4.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-16 14:07 EDT by Pawan Singh CLA
Modified: 2019-09-06 16:13 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pawan Singh CLA 2009-04-16 14:07:39 EDT
Build ID: M20080911-1700

Steps To Reproduce:
It is hard to reproduce - but happens often. It simply happens from time to time when shutting down our RCP application.


More information:
Here is the exception:

java.lang.RuntimeException: C:\Documents and Settings\hku\.iTestConfiguration_3.4\org.eclipse.osgi\.lazy.3 (The system cannot find the file specified)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.fullyLoad(BundleDescriptionImpl.java:489)
at org.eclipse.osgi.internal.resolver.BundleDescriptionImpl.getExportPackages(BundleDescriptionImpl.java:123)
at org.eclipse.osgi.internal.resolver.StateHelperImpl.addReference(StateHelperImpl.java:302)
at org.eclipse.osgi.internal.resolver.StateHelperImpl.buildReferences(StateHelperImpl.java:292)
at org.eclipse.osgi.internal.resolver.StateHelperImpl.buildReferences(StateHelperImpl.java:286)
at org.eclipse.osgi.internal.resolver.StateHelperImpl.sortBundles(StateHelperImpl.java:238)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.sortByDependencies(StartLevelManager.java:575)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.sortByDependency(StartLevelManager.java:556)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.getInstalledBundles(StartLevelManager.java:532)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:306)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(StartLevelManager.java:257)
at org.eclipse.osgi.framework.internal.core.SystemBundle.suspend(SystemBundle.java:236)
at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Framework.java:678)
at org.eclipse.osgi.framework.internal.core.Framework.close(Framework.java:576)
at org.eclipse.osgi.framework.internal.core.OSGi.close(OSGi.java:41)
at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(EclipseStarter.java:424)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:200)
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:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
Comment 1 Thomas Watson CLA 2009-04-16 14:27:12 EDT
Do you launch with -clean?  Do you run more than one instance of the RCP app at a time?

It seems like something has deleted the osgi cache while the platform is running (C:\Documents and Settings\hku\.iTestConfiguration_3.4\org.eclipse.osgi).  If you are using -clean then this could happen if you are trying to launch another instance while the first instance is trying to shutdown.

If that is not the case is there something else in your environment that would have deleted this folder?
Comment 2 Pawan Singh CLA 2009-04-16 14:31:01 EDT
We do run multiple instances of our RCP at one time. But we never run it with "-clean". There is nothing else in our environment which could have deleted that folder.

We do build new versions of RCP every day and run multiple instances of it for testing.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:13:11 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.