You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Dan Tran <da...@gmail.com> on 2013/02/09 06:14:13 UTC
Aries/JPA error to stdout at karaf 2.3.1-SNAPSHOT
I am testing out my app which has a few JPA bundle with karaf 2.3.1-SNAPSHOT
during shutdown, karaf throws the following error to stdout
ERROR: Bundle org.apache.aries.jpa.container [73] Error stopping
bundle. (java.lang.IllegalStateException: No persistence units defined
for bundle xxxx.host.mgr/1.0.0.SNAPSHOT.)
java.lang.IllegalStateException: No persistence units defined for
bundle xxxx.host.mgr/1.0.0.SNAPSHOT.
at org.apache.aries.jpa.container.unit.impl.ManagedPersistenceUnitInfoFactoryImpl.destroyPersistenceBundle(ManagedPersistenceUnitInfoFactoryImpl.java:60)
at org.apache.aries.jpa.container.impl.PersistenceBundleManager.removedBundle(PersistenceBundleManager.java:313)
at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:513)
at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:433)
This may be a regression under new blueprint's core?
my OpenJPA with embeded derby runs fine after startup. Only at
shutdown it barfs.
Thanks
-D
Re: Aries/JPA error to stdout at karaf 2.3.1-SNAPSHOT
Posted by Christoph Gritschenberger <ch...@gmail.com>.
Hi Dan,
I had time to investigate this a bit further and found the problem in
Aries-JPA. I filed ARIES-1018 [1].
regards,
christoph
[1] https://issues.apache.org/jira/browse/ARIES-1018
On 2013-02-22 20:37, Dan Tran wrote:
> Thanks I will give it a shot, and report back
>
> -D
>
> On Fri, Feb 22, 2013 at 9:00 AM, Christoph Gritschenberger
> <ch...@gmail.com> wrote:
>> Hi Dan,
>>
>> I ran into this issue recently myself (was working on a 4-week-old
>> karaf-trunk-version until now).
>>
>> I found a workaround for the problem:
>> I just set the start-level for the openjpa-bundle to 19 so it starts before
>> the Aries stuff.
>>
>> The Exception is thrown because the persistence-units are destroyed twice.
>> Once when the JPA-provider (OpenJPA-bundle) is shut down and once when
>> "Aries JPA Container" is shut down.
>> If the provider is shutdown after Aries, the Exception does not occur.
>>
>> regards,
>> christoph
>>
>>
>> On 2013-02-11 17:53, Dan Tran wrote:
>>>
>>> I am using jpa from karaf's enterprise feature. This means JPA start
>>> at system level ( ie 30 )
>>>
>>> -D
>>>
>>> On Mon, Feb 11, 2013 at 2:55 AM, Christoph Gritschenberger
>>> <ch...@gmail.com> wrote:
>>>>
>>>> Hi Dan,
>>>>
>>>> What's the start-level of your bundles?
>>>> I think I remember encountering this issue with bundles that started
>>>> before
>>>> aries-stuff.
>>>>
>>>> kind regards,
>>>> christoph
>>>>
>>>>
>>>> On 2013-02-10 23:22, Dan Tran wrote:
>>>>>
>>>>>
>>>>> H JB,
>>>>>
>>>>> I rebuild karaf-2.3.1-SNAPSHOT using aries.jpa 1.0.0 ( ie with
>>>>> -Daries.jpa.version=1.0.0 -Daries.jpa.container.context.version=1.0.0,
>>>>> see karaf-2.3.1-SNAPSHOT's top level pom for details) and still see
>>>>> the issue. So this probably comes from changes id needed
>>>>> aries.blueprint.core )
>>>>>
>>>>> -D
>>>>>
>>>>> On Sun, Feb 10, 2013 at 12:06 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
>>>>> wrote:
>>>>>>
>>>>>>
>>>>>> It seems that the JPA engine is now "mandatory". Let me take a look in
>>>>>> the
>>>>>> Aries JPA changes.
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>>
>>>>>> On 02/10/2013 09:02 PM, Dan Tran wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I wonder if any one who also uses JPA sees the same issue with me at
>>>>>>> karaf 2.3.1-snapshot?
>>>>>>>
>>>>>>> -D
>>>>>>>
>>>>>>> On Fri, Feb 8, 2013 at 9:14 PM, Dan Tran <da...@gmail.com> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> I am testing out my app which has a few JPA bundle with karaf
>>>>>>>> 2.3.1-SNAPSHOT
>>>>>>>>
>>>>>>>> during shutdown, karaf throws the following error to stdout
>>>>>>>>
>>>>>>>>
>>>>>>>> ERROR: Bundle org.apache.aries.jpa.container [73] Error stopping
>>>>>>>> bundle. (java.lang.IllegalStateException: No persistence units
>>>>>>>> defined
>>>>>>>> for bundle xxxx.host.mgr/1.0.0.SNAPSHOT.)
>>>>>>>> java.lang.IllegalStateException: No persistence units defined for
>>>>>>>> bundle xxxx.host.mgr/1.0.0.SNAPSHOT.
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.apache.aries.jpa.container.unit.impl.ManagedPersistenceUnitInfoFactoryImpl.destroyPersistenceBundle(ManagedPersistenceUnitInfoFactoryImpl.java:60)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.apache.aries.jpa.container.impl.PersistenceBundleManager.removedBundle(PersistenceBundleManager.java:313)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:513)
>>>>>>>> at
>>>>>>>>
>>>>>>>>
>>>>>>>> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:433)
>>>>>>>>
>>>>>>>>
>>>>>>>> This may be a regression under new blueprint's core?
>>>>>>>>
>>>>>>>> my OpenJPA with embeded derby runs fine after startup. Only at
>>>>>>>> shutdown it barfs.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>>
>>>>>>>> -D
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jean-Baptiste Onofré
>>>>>> jbonofre@apache.org
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>>
>>>>
>>
>>
Re: Aries/JPA error to stdout at karaf 2.3.1-SNAPSHOT
Posted by Dan Tran <da...@gmail.com>.
Thanks I will give it a shot, and report back
-D
On Fri, Feb 22, 2013 at 9:00 AM, Christoph Gritschenberger
<ch...@gmail.com> wrote:
> Hi Dan,
>
> I ran into this issue recently myself (was working on a 4-week-old
> karaf-trunk-version until now).
>
> I found a workaround for the problem:
> I just set the start-level for the openjpa-bundle to 19 so it starts before
> the Aries stuff.
>
> The Exception is thrown because the persistence-units are destroyed twice.
> Once when the JPA-provider (OpenJPA-bundle) is shut down and once when
> "Aries JPA Container" is shut down.
> If the provider is shutdown after Aries, the Exception does not occur.
>
> regards,
> christoph
>
>
> On 2013-02-11 17:53, Dan Tran wrote:
>>
>> I am using jpa from karaf's enterprise feature. This means JPA start
>> at system level ( ie 30 )
>>
>> -D
>>
>> On Mon, Feb 11, 2013 at 2:55 AM, Christoph Gritschenberger
>> <ch...@gmail.com> wrote:
>>>
>>> Hi Dan,
>>>
>>> What's the start-level of your bundles?
>>> I think I remember encountering this issue with bundles that started
>>> before
>>> aries-stuff.
>>>
>>> kind regards,
>>> christoph
>>>
>>>
>>> On 2013-02-10 23:22, Dan Tran wrote:
>>>>
>>>>
>>>> H JB,
>>>>
>>>> I rebuild karaf-2.3.1-SNAPSHOT using aries.jpa 1.0.0 ( ie with
>>>> -Daries.jpa.version=1.0.0 -Daries.jpa.container.context.version=1.0.0,
>>>> see karaf-2.3.1-SNAPSHOT's top level pom for details) and still see
>>>> the issue. So this probably comes from changes id needed
>>>> aries.blueprint.core )
>>>>
>>>> -D
>>>>
>>>> On Sun, Feb 10, 2013 at 12:06 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
>>>> wrote:
>>>>>
>>>>>
>>>>> It seems that the JPA engine is now "mandatory". Let me take a look in
>>>>> the
>>>>> Aries JPA changes.
>>>>>
>>>>> Regards
>>>>> JB
>>>>>
>>>>>
>>>>> On 02/10/2013 09:02 PM, Dan Tran wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> I wonder if any one who also uses JPA sees the same issue with me at
>>>>>> karaf 2.3.1-snapshot?
>>>>>>
>>>>>> -D
>>>>>>
>>>>>> On Fri, Feb 8, 2013 at 9:14 PM, Dan Tran <da...@gmail.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> I am testing out my app which has a few JPA bundle with karaf
>>>>>>> 2.3.1-SNAPSHOT
>>>>>>>
>>>>>>> during shutdown, karaf throws the following error to stdout
>>>>>>>
>>>>>>>
>>>>>>> ERROR: Bundle org.apache.aries.jpa.container [73] Error stopping
>>>>>>> bundle. (java.lang.IllegalStateException: No persistence units
>>>>>>> defined
>>>>>>> for bundle xxxx.host.mgr/1.0.0.SNAPSHOT.)
>>>>>>> java.lang.IllegalStateException: No persistence units defined for
>>>>>>> bundle xxxx.host.mgr/1.0.0.SNAPSHOT.
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.apache.aries.jpa.container.unit.impl.ManagedPersistenceUnitInfoFactoryImpl.destroyPersistenceBundle(ManagedPersistenceUnitInfoFactoryImpl.java:60)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.apache.aries.jpa.container.impl.PersistenceBundleManager.removedBundle(PersistenceBundleManager.java:313)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:513)
>>>>>>> at
>>>>>>>
>>>>>>>
>>>>>>> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:433)
>>>>>>>
>>>>>>>
>>>>>>> This may be a regression under new blueprint's core?
>>>>>>>
>>>>>>> my OpenJPA with embeded derby runs fine after startup. Only at
>>>>>>> shutdown it barfs.
>>>>>>>
>>>>>>> Thanks
>>>>>>>
>>>>>>> -D
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Jean-Baptiste Onofré
>>>>> jbonofre@apache.org
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>
>>>
>>>
>>>
>
>
Re: Aries/JPA error to stdout at karaf 2.3.1-SNAPSHOT
Posted by Christoph Gritschenberger <ch...@gmail.com>.
Hi Dan,
I ran into this issue recently myself (was working on a 4-week-old
karaf-trunk-version until now).
I found a workaround for the problem:
I just set the start-level for the openjpa-bundle to 19 so it starts
before the Aries stuff.
The Exception is thrown because the persistence-units are destroyed
twice. Once when the JPA-provider (OpenJPA-bundle) is shut down and once
when "Aries JPA Container" is shut down.
If the provider is shutdown after Aries, the Exception does not occur.
regards,
christoph
On 2013-02-11 17:53, Dan Tran wrote:
> I am using jpa from karaf's enterprise feature. This means JPA start
> at system level ( ie 30 )
>
> -D
>
> On Mon, Feb 11, 2013 at 2:55 AM, Christoph Gritschenberger
> <ch...@gmail.com> wrote:
>> Hi Dan,
>>
>> What's the start-level of your bundles?
>> I think I remember encountering this issue with bundles that started before
>> aries-stuff.
>>
>> kind regards,
>> christoph
>>
>>
>> On 2013-02-10 23:22, Dan Tran wrote:
>>>
>>> H JB,
>>>
>>> I rebuild karaf-2.3.1-SNAPSHOT using aries.jpa 1.0.0 ( ie with
>>> -Daries.jpa.version=1.0.0 -Daries.jpa.container.context.version=1.0.0,
>>> see karaf-2.3.1-SNAPSHOT's top level pom for details) and still see
>>> the issue. So this probably comes from changes id needed
>>> aries.blueprint.core )
>>>
>>> -D
>>>
>>> On Sun, Feb 10, 2013 at 12:06 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
>>> wrote:
>>>>
>>>> It seems that the JPA engine is now "mandatory". Let me take a look in
>>>> the
>>>> Aries JPA changes.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>
>>>> On 02/10/2013 09:02 PM, Dan Tran wrote:
>>>>>
>>>>>
>>>>> I wonder if any one who also uses JPA sees the same issue with me at
>>>>> karaf 2.3.1-snapshot?
>>>>>
>>>>> -D
>>>>>
>>>>> On Fri, Feb 8, 2013 at 9:14 PM, Dan Tran <da...@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>> I am testing out my app which has a few JPA bundle with karaf
>>>>>> 2.3.1-SNAPSHOT
>>>>>>
>>>>>> during shutdown, karaf throws the following error to stdout
>>>>>>
>>>>>>
>>>>>> ERROR: Bundle org.apache.aries.jpa.container [73] Error stopping
>>>>>> bundle. (java.lang.IllegalStateException: No persistence units defined
>>>>>> for bundle xxxx.host.mgr/1.0.0.SNAPSHOT.)
>>>>>> java.lang.IllegalStateException: No persistence units defined for
>>>>>> bundle xxxx.host.mgr/1.0.0.SNAPSHOT.
>>>>>> at
>>>>>>
>>>>>> org.apache.aries.jpa.container.unit.impl.ManagedPersistenceUnitInfoFactoryImpl.destroyPersistenceBundle(ManagedPersistenceUnitInfoFactoryImpl.java:60)
>>>>>> at
>>>>>>
>>>>>> org.apache.aries.jpa.container.impl.PersistenceBundleManager.removedBundle(PersistenceBundleManager.java:313)
>>>>>> at
>>>>>>
>>>>>> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:513)
>>>>>> at
>>>>>>
>>>>>> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:433)
>>>>>>
>>>>>>
>>>>>> This may be a regression under new blueprint's core?
>>>>>>
>>>>>> my OpenJPA with embeded derby runs fine after startup. Only at
>>>>>> shutdown it barfs.
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> -D
>>>>
>>>>
>>>>
>>>> --
>>>> Jean-Baptiste Onofré
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>
>>
>>
Re: Aries/JPA error to stdout at karaf 2.3.1-SNAPSHOT
Posted by Dan Tran <da...@gmail.com>.
I am using jpa from karaf's enterprise feature. This means JPA start
at system level ( ie 30 )
-D
On Mon, Feb 11, 2013 at 2:55 AM, Christoph Gritschenberger
<ch...@gmail.com> wrote:
> Hi Dan,
>
> What's the start-level of your bundles?
> I think I remember encountering this issue with bundles that started before
> aries-stuff.
>
> kind regards,
> christoph
>
>
> On 2013-02-10 23:22, Dan Tran wrote:
>>
>> H JB,
>>
>> I rebuild karaf-2.3.1-SNAPSHOT using aries.jpa 1.0.0 ( ie with
>> -Daries.jpa.version=1.0.0 -Daries.jpa.container.context.version=1.0.0,
>> see karaf-2.3.1-SNAPSHOT's top level pom for details) and still see
>> the issue. So this probably comes from changes id needed
>> aries.blueprint.core )
>>
>> -D
>>
>> On Sun, Feb 10, 2013 at 12:06 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
>> wrote:
>>>
>>> It seems that the JPA engine is now "mandatory". Let me take a look in
>>> the
>>> Aries JPA changes.
>>>
>>> Regards
>>> JB
>>>
>>>
>>> On 02/10/2013 09:02 PM, Dan Tran wrote:
>>>>
>>>>
>>>> I wonder if any one who also uses JPA sees the same issue with me at
>>>> karaf 2.3.1-snapshot?
>>>>
>>>> -D
>>>>
>>>> On Fri, Feb 8, 2013 at 9:14 PM, Dan Tran <da...@gmail.com> wrote:
>>>>>
>>>>>
>>>>> I am testing out my app which has a few JPA bundle with karaf
>>>>> 2.3.1-SNAPSHOT
>>>>>
>>>>> during shutdown, karaf throws the following error to stdout
>>>>>
>>>>>
>>>>> ERROR: Bundle org.apache.aries.jpa.container [73] Error stopping
>>>>> bundle. (java.lang.IllegalStateException: No persistence units defined
>>>>> for bundle xxxx.host.mgr/1.0.0.SNAPSHOT.)
>>>>> java.lang.IllegalStateException: No persistence units defined for
>>>>> bundle xxxx.host.mgr/1.0.0.SNAPSHOT.
>>>>> at
>>>>>
>>>>> org.apache.aries.jpa.container.unit.impl.ManagedPersistenceUnitInfoFactoryImpl.destroyPersistenceBundle(ManagedPersistenceUnitInfoFactoryImpl.java:60)
>>>>> at
>>>>>
>>>>> org.apache.aries.jpa.container.impl.PersistenceBundleManager.removedBundle(PersistenceBundleManager.java:313)
>>>>> at
>>>>>
>>>>> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:513)
>>>>> at
>>>>>
>>>>> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:433)
>>>>>
>>>>>
>>>>> This may be a regression under new blueprint's core?
>>>>>
>>>>> my OpenJPA with embeded derby runs fine after startup. Only at
>>>>> shutdown it barfs.
>>>>>
>>>>> Thanks
>>>>>
>>>>> -D
>>>
>>>
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>
>
>
Re: Aries/JPA error to stdout at karaf 2.3.1-SNAPSHOT
Posted by Christoph Gritschenberger <ch...@gmail.com>.
Hi Dan,
What's the start-level of your bundles?
I think I remember encountering this issue with bundles that started
before aries-stuff.
kind regards,
christoph
On 2013-02-10 23:22, Dan Tran wrote:
> H JB,
>
> I rebuild karaf-2.3.1-SNAPSHOT using aries.jpa 1.0.0 ( ie with
> -Daries.jpa.version=1.0.0 -Daries.jpa.container.context.version=1.0.0,
> see karaf-2.3.1-SNAPSHOT's top level pom for details) and still see
> the issue. So this probably comes from changes id needed
> aries.blueprint.core )
>
> -D
>
> On Sun, Feb 10, 2013 at 12:06 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>> It seems that the JPA engine is now "mandatory". Let me take a look in the
>> Aries JPA changes.
>>
>> Regards
>> JB
>>
>>
>> On 02/10/2013 09:02 PM, Dan Tran wrote:
>>>
>>> I wonder if any one who also uses JPA sees the same issue with me at
>>> karaf 2.3.1-snapshot?
>>>
>>> -D
>>>
>>> On Fri, Feb 8, 2013 at 9:14 PM, Dan Tran <da...@gmail.com> wrote:
>>>>
>>>> I am testing out my app which has a few JPA bundle with karaf
>>>> 2.3.1-SNAPSHOT
>>>>
>>>> during shutdown, karaf throws the following error to stdout
>>>>
>>>>
>>>> ERROR: Bundle org.apache.aries.jpa.container [73] Error stopping
>>>> bundle. (java.lang.IllegalStateException: No persistence units defined
>>>> for bundle xxxx.host.mgr/1.0.0.SNAPSHOT.)
>>>> java.lang.IllegalStateException: No persistence units defined for
>>>> bundle xxxx.host.mgr/1.0.0.SNAPSHOT.
>>>> at
>>>> org.apache.aries.jpa.container.unit.impl.ManagedPersistenceUnitInfoFactoryImpl.destroyPersistenceBundle(ManagedPersistenceUnitInfoFactoryImpl.java:60)
>>>> at
>>>> org.apache.aries.jpa.container.impl.PersistenceBundleManager.removedBundle(PersistenceBundleManager.java:313)
>>>> at
>>>> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:513)
>>>> at
>>>> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:433)
>>>>
>>>>
>>>> This may be a regression under new blueprint's core?
>>>>
>>>> my OpenJPA with embeded derby runs fine after startup. Only at
>>>> shutdown it barfs.
>>>>
>>>> Thanks
>>>>
>>>> -D
>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
Re: Aries/JPA error to stdout at karaf 2.3.1-SNAPSHOT
Posted by Dan Tran <da...@gmail.com>.
H JB,
I rebuild karaf-2.3.1-SNAPSHOT using aries.jpa 1.0.0 ( ie with
-Daries.jpa.version=1.0.0 -Daries.jpa.container.context.version=1.0.0,
see karaf-2.3.1-SNAPSHOT's top level pom for details) and still see
the issue. So this probably comes from changes id needed
aries.blueprint.core )
-D
On Sun, Feb 10, 2013 at 12:06 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> It seems that the JPA engine is now "mandatory". Let me take a look in the
> Aries JPA changes.
>
> Regards
> JB
>
>
> On 02/10/2013 09:02 PM, Dan Tran wrote:
>>
>> I wonder if any one who also uses JPA sees the same issue with me at
>> karaf 2.3.1-snapshot?
>>
>> -D
>>
>> On Fri, Feb 8, 2013 at 9:14 PM, Dan Tran <da...@gmail.com> wrote:
>>>
>>> I am testing out my app which has a few JPA bundle with karaf
>>> 2.3.1-SNAPSHOT
>>>
>>> during shutdown, karaf throws the following error to stdout
>>>
>>>
>>> ERROR: Bundle org.apache.aries.jpa.container [73] Error stopping
>>> bundle. (java.lang.IllegalStateException: No persistence units defined
>>> for bundle xxxx.host.mgr/1.0.0.SNAPSHOT.)
>>> java.lang.IllegalStateException: No persistence units defined for
>>> bundle xxxx.host.mgr/1.0.0.SNAPSHOT.
>>> at
>>> org.apache.aries.jpa.container.unit.impl.ManagedPersistenceUnitInfoFactoryImpl.destroyPersistenceBundle(ManagedPersistenceUnitInfoFactoryImpl.java:60)
>>> at
>>> org.apache.aries.jpa.container.impl.PersistenceBundleManager.removedBundle(PersistenceBundleManager.java:313)
>>> at
>>> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:513)
>>> at
>>> org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:433)
>>>
>>>
>>> This may be a regression under new blueprint's core?
>>>
>>> my OpenJPA with embeded derby runs fine after startup. Only at
>>> shutdown it barfs.
>>>
>>> Thanks
>>>
>>> -D
>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
Re: Aries/JPA error to stdout at karaf 2.3.1-SNAPSHOT
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
It seems that the JPA engine is now "mandatory". Let me take a look in
the Aries JPA changes.
Regards
JB
On 02/10/2013 09:02 PM, Dan Tran wrote:
> I wonder if any one who also uses JPA sees the same issue with me at
> karaf 2.3.1-snapshot?
>
> -D
>
> On Fri, Feb 8, 2013 at 9:14 PM, Dan Tran <da...@gmail.com> wrote:
>> I am testing out my app which has a few JPA bundle with karaf 2.3.1-SNAPSHOT
>>
>> during shutdown, karaf throws the following error to stdout
>>
>>
>> ERROR: Bundle org.apache.aries.jpa.container [73] Error stopping
>> bundle. (java.lang.IllegalStateException: No persistence units defined
>> for bundle xxxx.host.mgr/1.0.0.SNAPSHOT.)
>> java.lang.IllegalStateException: No persistence units defined for
>> bundle xxxx.host.mgr/1.0.0.SNAPSHOT.
>> at org.apache.aries.jpa.container.unit.impl.ManagedPersistenceUnitInfoFactoryImpl.destroyPersistenceBundle(ManagedPersistenceUnitInfoFactoryImpl.java:60)
>> at org.apache.aries.jpa.container.impl.PersistenceBundleManager.removedBundle(PersistenceBundleManager.java:313)
>> at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:513)
>> at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:433)
>>
>>
>> This may be a regression under new blueprint's core?
>>
>> my OpenJPA with embeded derby runs fine after startup. Only at
>> shutdown it barfs.
>>
>> Thanks
>>
>> -D
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Aries/JPA error to stdout at karaf 2.3.1-SNAPSHOT
Posted by Dan Tran <da...@gmail.com>.
I wonder if any one who also uses JPA sees the same issue with me at
karaf 2.3.1-snapshot?
-D
On Fri, Feb 8, 2013 at 9:14 PM, Dan Tran <da...@gmail.com> wrote:
> I am testing out my app which has a few JPA bundle with karaf 2.3.1-SNAPSHOT
>
> during shutdown, karaf throws the following error to stdout
>
>
> ERROR: Bundle org.apache.aries.jpa.container [73] Error stopping
> bundle. (java.lang.IllegalStateException: No persistence units defined
> for bundle xxxx.host.mgr/1.0.0.SNAPSHOT.)
> java.lang.IllegalStateException: No persistence units defined for
> bundle xxxx.host.mgr/1.0.0.SNAPSHOT.
> at org.apache.aries.jpa.container.unit.impl.ManagedPersistenceUnitInfoFactoryImpl.destroyPersistenceBundle(ManagedPersistenceUnitInfoFactoryImpl.java:60)
> at org.apache.aries.jpa.container.impl.PersistenceBundleManager.removedBundle(PersistenceBundleManager.java:313)
> at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:513)
> at org.apache.aries.util.tracker.hook.BundleHookBundleTracker$Tracked.customizerRemoved(BundleHookBundleTracker.java:433)
>
>
> This may be a regression under new blueprint's core?
>
> my OpenJPA with embeded derby runs fine after startup. Only at
> shutdown it barfs.
>
> Thanks
>
> -D