aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <>
Subject [jira] [Commented] (ARIES-1018) JPA container throws Exception when stopped without a JPA-Provider present
Date Thu, 28 Feb 2013 07:35:13 GMT


Guillaume Nodet commented on ARIES-1018:

Yeah, that may definitely be a regression caused by the change I made to the bundle tracker.
The jpa container should support that better, as the tracker should really untrack all bundles,
as it's done with the usual BundleTracker.
> JPA container throws Exception when stopped without a JPA-Provider present
> --------------------------------------------------------------------------
>                 Key: ARIES-1018
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>          Components: JPA
>         Environment: karaf 3.0.0-SNAPSHOT, KARAF-2.3.1-SHAPSHOT
>            Reporter: Christoph Gritschenberger
> To reproduce unpack the latest karaf-snapshot and install the JPA-feature:
> {code}
> feature:install jpa
> {code}
> and install a bundle containing a persistence-unit.
> stop the JPA Container bundle.
> {code}
> {code}
> This happens since aries-util was upgraded to 1.1.0. The issue did not occur with util-1.0.0.
> I investigated a bit and found the problem:
> In util-1.1.0 the BundleHookBundleTracker was changed to untrack all bundles when it's
closed. In util-1.0 closing did essentially nothing but setting a closed-flag.
> So when using JPA Container with util-1.1.0 the persistence-units are destroyed without
ever being created.
> This also happens when having a JPA Provider (like OpenJPA) installed, but when it's
stopped before the the JPA-Container Bundle is stopped (the usual case).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message