Re: [osgi-dev] Shutdown order
Hi, Here is an example log starting with a few of the previous normal logged entries. We can see that for o.e.debug.core and then for org.eclipse.sirius.viewpoint.SiriusPlugin they are both failing since the Workspace is closed. Thanks Alain 16:29:22.367 [Framework stop] INFO c.c.i.b.d.p.f.DiagramHandlerFactory - Removing descriptor provider Base/BaseLink/BaseValue/ValueSubStages 16:29:22.367 [Framework stop] INFO c.c.i.b.d.p.f.DiagramHandlerFactory - Removing notification provider Base/BaseLink/BaseValue/ValueSubStages 16:29:22.391 [Framework stop] INFO o.a.a.j.r.w.a.CxfJaxrsBundleActivator - Unregistered SseEventSourceFactory 16:29:22.391 [Framework stop] INFO o.a.a.j.r.w.a.CxfJaxrsBundleActivator - Unregistered ClientBuilder !ENTRY org.eclipse.debug.core 4 0 2019-08-12 16:29:22.516 !MESSAGE FrameworkEvent ERROR !STACK 0 org.osgi.framework.BundleException: Exception in org.eclipse.debug.core.DebugPlugin.stop() of bundle org.eclipse.debug.core. at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:855) at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:947) at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:314) at org.eclipse.osgi.container.Module.doStop(Module.java:636) at org.eclipse.osgi.container.Module.stop(Module.java:498) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1669) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1588) at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:270) at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:147) at org.eclipse.osgi.container.Module.doStop(Module.java:636) at org.eclipse.osgi.container.Module.stop(Module.java:498) at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:202) at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.IllegalStateException: Workspace is closed. at org.eclipse.core.resources.ResourcesPlugin.getWorkspace(ResourcesPlugin.java:412) at org.eclipse.debug.internal.core.LaunchManager.hookResourceChangeListener(LaunchManager.java:1897) at org.eclipse.debug.internal.core.LaunchManager.initializeLaunchConfigurationTypes(LaunchManager.java:1932) at org.eclipse.debug.internal.core.LaunchManager.getLaunchConfigurationTypes(LaunchManager.java:1484) at org.eclipse.debug.internal.core.LaunchManager.persistPreferredLaunchDelegates(LaunchManager.java:2405) at org.eclipse.debug.internal.core.LaunchManager.shutdown(LaunchManager.java:2393) at org.eclipse.debug.core.DebugPlugin.stop(DebugPlugin.java:661) at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:835) at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:828) ... 13 more Root exception: java.lang.IllegalStateException: Workspace is closed. at org.eclipse.core.resources.ResourcesPlugin.getWorkspace(ResourcesPlugin.java:412) at org.eclipse.debug.internal.core.LaunchManager.hookResourceChangeListener(LaunchManager.java:1897) at org.eclipse.debug.internal.core.LaunchManager.initializeLaunchConfigurationTypes(LaunchManager.java:1932) at org.eclipse.debug.internal.core.LaunchManager.getLaunchConfigurationTypes(LaunchManager.java:1484) at org.eclipse.debug.internal.core.LaunchManager.persistPreferredLaunchDelegates(LaunchManager.java:2405) at org.eclipse.debug.internal.core.LaunchManager.shutdown(LaunchManager.java:2393) at org.eclipse.debug.core.DebugPlugin.stop(DebugPlugin.java:661) at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:835) at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1) at java.security.AccessController.doPrivileged(Native Method) at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:828) at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:947) at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:314) at org.eclipse.osgi.container.Module.doStop(Module.java:636) at org.eclipse.osgi.container.Module.stop(Module.java:498) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1669) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1588) at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:270) at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:147) at
Re: [osgi-dev] Shutdown order
Perhaps platform depends upon something which is no longer active? Since these exceptions seem to be from Eclipse plugins, perhaps Eclipse people can be of more specific help here? From the spec point of view, bundles in higher start levels are stopped before bundles at lower start levels. I would assume that the Equinox framework is correct here. So the issue would be in the Eclipse bundles. --BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com - Original message -From: Alain Picard via osgi-dev Sent by: osgi-dev-boun...@mail.osgi.orgTo: OSGi Developer Mail List Cc:Subject: [EXTERNAL] [osgi-dev] Shutdown orderDate: Sat, Aug 10, 2019 08:13 Hi, I'm getting some exceptions when invoking shutdown. Some of those come from Eclipse plugins that expect the Platform to exist (from o.e.core.runtime). I was reading section 9.3.1 and expected that if o.e.core.runtime start level would be lower then it would be stopped later in the process as the level is decremented by 1. This didn't stop the exception (similar to what was reported here). What am I missing? Or what can I do. Cheers, Alain ___OSGi Developer Mail Listosgi-dev@mail.osgi.orghttps://mail.osgi.org/mailman/listinfo/osgi-dev ___ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
