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/08/20 16:16:54 UTC

[DISCUSS] Apache Aries (Incubating) version 0.2-incubating release candidate 02

Hi

Just starting a thread for discussion of Aries 0.2-incubating release 
candidate 02.

Zoë

RE: [DISCUSS] Apache Aries (Incubating) version 0.2-incubating release candidate 02

Posted by Timothy Ward <ti...@hotmail.com>.
That failure is benign, and has a simple fix. I'll put a change into trunk and the release branch. Is there a JIRA for this?

Tim

----------------------------------------
> Date: Mon, 23 Aug 2010 02:05:31 -0400
> Subject: Re: [DISCUSS] Apache Aries (Incubating) version 0.2-incubating release candidate 02
> From: jgawor@gmail.com
> To: aries-dev@incubator.apache.org
>
> I will do more testing tomorrow but so far I've noticed the following:
>
> java.lang.NullPointerException
> at org.apache.aries.jpa.container.impl.PersistenceBundleManager.stop(PersistenceBundleManager.java:641)
> at org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:655)
> at org.apache.felix.framework.Felix.stopBundle(Felix.java:2190)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1172)
> at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
> at java.lang.Thread.run(Thread.java:619)
>
> It doesn't look critical but a bit annoying.
>
> Jarek
>
> On Fri, Aug 20, 2010 at 10:16 AM, zoe slattery  wrote:
>> Hi
>>
>> Just starting a thread for discussion of Aries 0.2-incubating release
>> candidate 02.
>>
>> Zoė
>>

Re: [DISCUSS] Apache Aries (Incubating) version 0.2-incubating release candidate 02

Posted by Lin Sun <li...@gmail.com>.
I ran into this error constantly, too

Lin

On Mon, Aug 23, 2010 at 2:05 AM, Jarek Gawor <jg...@gmail.com> wrote:
> I will do more testing tomorrow but so far I've noticed the following:
>
> java.lang.NullPointerException
>        at org.apache.aries.jpa.container.impl.PersistenceBundleManager.stop(PersistenceBundleManager.java:641)
>        at org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:655)
>        at org.apache.felix.framework.Felix.stopBundle(Felix.java:2190)
>        at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1172)
>        at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
>        at java.lang.Thread.run(Thread.java:619)
>
> It doesn't look critical but a bit annoying.
>
> Jarek
>
> On Fri, Aug 20, 2010 at 10:16 AM, zoe slattery <zo...@gmail.com> wrote:
>> Hi
>>
>> Just starting a thread for discussion of Aries 0.2-incubating release
>> candidate 02.
>>
>> Zoė
>>
>

Re: [DISCUSS] Apache Aries (Incubating) version 0.2-incubating release candidate 02

Posted by Jarek Gawor <jg...@gmail.com>.
I will do more testing tomorrow but so far I've noticed the following:

java.lang.NullPointerException
	at org.apache.aries.jpa.container.impl.PersistenceBundleManager.stop(PersistenceBundleManager.java:641)
	at org.apache.felix.framework.util.SecureAction.stopActivator(SecureAction.java:655)
	at org.apache.felix.framework.Felix.stopBundle(Felix.java:2190)
	at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1172)
	at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
	at java.lang.Thread.run(Thread.java:619)

It doesn't look critical but a bit annoying.

Jarek

On Fri, Aug 20, 2010 at 10:16 AM, zoe slattery <zo...@gmail.com> wrote:
> Hi
>
> Just starting a thread for discussion of Aries 0.2-incubating release
> candidate 02.
>
> Zoė
>

Re: [DISCUSS] Apache Aries (Incubating) version 0.2-incubating release candidate 02

Posted by zoe slattery <zo...@gmail.com>.
Joe Bohn wrote:
> I just noticed that the URL for the parent source archive is incorrect 
> in the Vote notice.  This is the correct URL:
>
> 1. parent
> https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/parent/0.2-incubating/parent-0.2-incubating-source-release.zip 
>
Ach - thanks.
Z
>
> Joe
>
> On 8/20/10 10:16 AM, zoe slattery wrote:
>> Hi
>>
>> Just starting a thread for discussion of Aries 0.2-incubating release
>> candidate 02.
>>
>> Zoë
>>
>

Re: [DISCUSS] Apache Aries (Incubating) version 0.2-incubating release candidate 02

Posted by Joe Bohn <jo...@gmail.com>.
I just noticed that the URL for the parent source archive is incorrect 
in the Vote notice.  This is the correct URL:

1. parent
https://repository.apache.org/content/repositories/orgapachearies-113/org/apache/aries/parent/0.2-incubating/parent-0.2-incubating-source-release.zip

Joe

On 8/20/10 10:16 AM, zoe slattery wrote:
> Hi
>
> Just starting a thread for discussion of Aries 0.2-incubating release
> candidate 02.
>
> Zoë
>

Re: [DISCUSS] Apache Aries (Incubating) version 0.2-incubating release candidate 02

Posted by Joe Bohn <jo...@gmail.com>.
Hi Tim,

Yes, you are correct that it isn't an error.  I was fooled by seeing the 
exception (which I typically associate with an error).  Thanks for 
volunteering to remove the exception from the log.

All,
I'm not sure if it is worth trying to get this into the next 
0.2-incubating vote.  As Tim mentions, it isn't really an error.  But it 
might look strange to our users when running samples.  When I was going 
to fix this by including the quiesce bundles in the sample assemblies I 
thought it would be worth-while to respin samples.  Given that it is now 
a change to jpa should respin the jpa modules?

Joe


On 8/23/10 11:54 AM, Timothy Ward wrote:
>
> Hi,
>
> This isn't actually an error, which is why it's output as an info message. The stack trace does make it slightly confusing though, so I'll remove the exception from the log output.
>
> Tim
>
> ----------------------------------------
>> Date: Mon, 23 Aug 2010 11:46:41 -0400
>> From: joebohn@gmail.com
>> To: aries-dev@incubator.apache.org
>> Subject: Re: [DISCUSS] Apache Aries (Incubating) version 0.2-incubating release candidate 02
>>
>>
>> There is one other minor issue that I noticed with our samples that I'd
>> like to fix.
>>
>> We're getting the following exception when starting our sample
>> assemblies which I suspect is because of the new dependency from the jpa
>> bundle on quiesce. We don't currently include the quiesce bundle in our
>> assemblies and hence I suspect the following error. AFAIK it isn't
>> causing any real problem - just the exception when starting the assembly.
>>
>> I'll try adding in the quiesce bundle and if that resolves the issue
>> I'll create a JIRA and check it into trunk. We can then decide if we'd
>> like to include it a new 0.2-incubating sample release for the next vote.
>>
>> Here's the error:
>> [Start Level Event Dispatcher] DEBUG org.apache.aries.jpa.container -
>> Adding a provider:
>> {javax.persistence.spi.PersistenceProvider}={javax.persistence.provider=org.apache.openjpa.persistence.PersistenceProviderImpl,
>> service.id=39}
>> [Start Level Event Dispatcher] INFO org.apache.aries.jpa.container - No
>> quiesce support is available, so persistence contexts 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.jpa.container.impl.PersistenceBundleManager.start(PersistenceBundleManager.java:622)
>> 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)
>>
>> JPA on quiesce
>>
>>
>> On 8/20/10 10:16 AM, zoe slattery wrote:
>>> Hi
>>>
>>> Just starting a thread for discussion of Aries 0.2-incubating release
>>> candidate 02.
>>>
>>> Zoë
>>>
>>
>>
>> --
>> Joe
>   		 	   		


-- 
Joe

RE: [DISCUSS] Apache Aries (Incubating) version 0.2-incubating release candidate 02

Posted by Timothy Ward <ti...@hotmail.com>.
Hi,

This isn't actually an error, which is why it's output as an info message. The stack trace does make it slightly confusing though, so I'll remove the exception from the log output.

Tim 

----------------------------------------
> Date: Mon, 23 Aug 2010 11:46:41 -0400
> From: joebohn@gmail.com
> To: aries-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Apache Aries (Incubating) version 0.2-incubating release candidate 02
>
>
> There is one other minor issue that I noticed with our samples that I'd
> like to fix.
>
> We're getting the following exception when starting our sample
> assemblies which I suspect is because of the new dependency from the jpa
> bundle on quiesce. We don't currently include the quiesce bundle in our
> assemblies and hence I suspect the following error. AFAIK it isn't
> causing any real problem - just the exception when starting the assembly.
>
> I'll try adding in the quiesce bundle and if that resolves the issue
> I'll create a JIRA and check it into trunk. We can then decide if we'd
> like to include it a new 0.2-incubating sample release for the next vote.
>
> Here's the error:
> [Start Level Event Dispatcher] DEBUG org.apache.aries.jpa.container -
> Adding a provider:
> {javax.persistence.spi.PersistenceProvider}={javax.persistence.provider=org.apache.openjpa.persistence.PersistenceProviderImpl,
> service.id=39}
> [Start Level Event Dispatcher] INFO org.apache.aries.jpa.container - No
> quiesce support is available, so persistence contexts 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.jpa.container.impl.PersistenceBundleManager.start(PersistenceBundleManager.java:622)
> 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)
>
> JPA on quiesce
>
>
> On 8/20/10 10:16 AM, zoe slattery wrote:
>> Hi
>>
>> Just starting a thread for discussion of Aries 0.2-incubating release
>> candidate 02.
>>
>> Zoë
>>
>
>
> --
> Joe

Re: [DISCUSS] Apache Aries (Incubating) version 0.2-incubating release candidate 02

Posted by Joe Bohn <jo...@gmail.com>.
There is one other minor issue that I noticed with our samples that I'd 
like to fix.

We're getting the following exception when starting our sample 
assemblies which I suspect is because of the new dependency from the jpa 
bundle on quiesce.  We don't currently include the quiesce bundle in our 
assemblies and hence I suspect the following error.  AFAIK it isn't 
causing any real problem - just the exception when starting the assembly.

I'll try adding in the quiesce bundle and if that resolves the issue 
I'll create a JIRA and check it into trunk.  We can then decide if we'd 
like to include it a new 0.2-incubating sample release for the next vote.

Here's the error:
[Start Level Event Dispatcher] DEBUG org.apache.aries.jpa.container - 
Adding a provider: 
{javax.persistence.spi.PersistenceProvider}={javax.persistence.provider=org.apache.openjpa.persistence.PersistenceProviderImpl, 
service.id=39}
[Start Level Event Dispatcher] INFO org.apache.aries.jpa.container - No 
quiesce support is available, so persistence contexts 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.jpa.container.impl.PersistenceBundleManager.start(PersistenceBundleManager.java:622)
         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)

JPA on quiesce


On 8/20/10 10:16 AM, zoe slattery wrote:
> Hi
>
> Just starting a thread for discussion of Aries 0.2-incubating release
> candidate 02.
>
> Zoë
>


-- 
Joe

Re: [DISCUSS] Apache Aries (Incubating) version 0.2-incubating release candidate 02

Posted by Joe Bohn <jo...@gmail.com>.
I should probably start an new thread on versions ... but this 
particular question is pertinent to this vote so I'll raise it here first:

- We introduced a new component with this vote - quiesce.  In the vote 
we are releasing this as 0.2-incubating which implies that there might 
have been a 0.1-incubating.  Is this how we want to introduce this and 
future components - using the prevailing version of the vote?

Regards,
Joe


On 8/20/10 10:16 AM, zoe slattery wrote:
> Hi
>
> Just starting a thread for discussion of Aries 0.2-incubating release
> candidate 02.
>
> Zoë
>