You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by zoe slattery <zo...@gmail.com> on 2010/09/22 10:15:40 UTC

Blueprint dependency on Quiesce?

  Hi - not sure if this is intended but I get the following from the 
Blog sample. I can probably fix by adding quiesce to the 
dependencies...but should I have to?


[Start Level Event Dispatcher] INFO 
org.apache.aries.blueprint.container.BlueprintExtender - No quiesce 
support is available, so blueprint components will not participate in 
quiesce operations
java.lang.ClassNotFoundException: 
org.apache.aries.quiesce.participant.QuiesceParticipant
     at 
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489)
     at 
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
     at 
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
     at 
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
     at 
org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:321)
     at 
org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:231)
     at 
org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1193)
     at 
org.apache.aries.blueprint.container.BlueprintExtender.start(BlueprintExtender.java:96)
     at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782)
     at java.security.AccessController.doPrivileged(Native Method)
     at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773)
     at 
org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754)
     at 
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
     at 
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
     at 
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
     at 
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
     at 
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
     at 
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
     at 
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
     at 
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
     at 
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330

Re: Blueprint dependency on Quiesce?

Posted by Alasdair Nottingham <no...@apache.org>.
Certainly if it is info level it should be a nice pretty friendly message.

On 22 September 2010 01:18, Timothy Ward <ti...@hotmail.com> wrote:
>
> As with the JPA container, this info message is expected from blueprint if Quiesce isn't in the runtime. It probably shouldn't output a big scary stack trace though!
>
> Tim
>
> ----------------------------------------
>> Date: Wed, 22 Sep 2010 09:15:40 +0100
>> From: zoe.slattery@gmail.com
>> To: aries-dev@incubator.apache.org
>> Subject: Blueprint dependency on Quiesce?
>>
>> Hi - not sure if this is intended but I get the following from the
>> Blog sample. I can probably fix by adding quiesce to the
>> dependencies...but should I have to?
>>
>>
>> [Start Level Event Dispatcher] INFO
>> org.apache.aries.blueprint.container.BlueprintExtender - No quiesce
>> support is available, so blueprint components will not participate in
>> quiesce operations
>> java.lang.ClassNotFoundException:
>> org.apache.aries.quiesce.participant.QuiesceParticipant
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
>> at
>> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
>> at
>> org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:321)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:231)
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1193)
>> at
>> org.apache.aries.blueprint.container.BlueprintExtender.start(BlueprintExtender.java:96)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782)
>> at java.security.AccessController.doPrivileged(Native Method)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754)
>> at
>> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
>> at
>> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
>> at
>> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
>> at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
>> at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
>> at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
>> at
>> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
>> at
>> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330
>



-- 
Alasdair Nottingham
not@apache.org

RE: Blueprint dependency on Quiesce?

Posted by Timothy Ward <ti...@hotmail.com>.
As with the JPA container, this info message is expected from blueprint if Quiesce isn't in the runtime. It probably shouldn't output a big scary stack trace though!

Tim

----------------------------------------
> Date: Wed, 22 Sep 2010 09:15:40 +0100
> From: zoe.slattery@gmail.com
> To: aries-dev@incubator.apache.org
> Subject: Blueprint dependency on Quiesce?
>
> Hi - not sure if this is intended but I get the following from the
> Blog sample. I can probably fix by adding quiesce to the
> dependencies...but should I have to?
>
>
> [Start Level Event Dispatcher] INFO
> org.apache.aries.blueprint.container.BlueprintExtender - No quiesce
> support is available, so blueprint components will not participate in
> quiesce operations
> java.lang.ClassNotFoundException:
> org.apache.aries.quiesce.participant.QuiesceParticipant
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:489)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:405)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:393)
> at
> org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> at
> org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:321)
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:231)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1193)
> at
> org.apache.aries.blueprint.container.BlueprintExtender.start(BlueprintExtender.java:96)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$1.run(BundleContextImpl.java:782)
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:773)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:754)
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:352)
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
> at
> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
> at
> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330