[ARIES-1018] JPA container throws Exception when stopped without a JPA-Provider present

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Component/s: JPA

Environment

karaf 3.0.0-SNAPSHOT, KARAF-2.3.1-SHAPSHOT

• Assignee: Jean-Baptiste Onofré
• Reporter: Christoph Gritschenberger
• Created: 25/Feb/13 09:24
• Updated: 14/Jul/14 12:57
• Resolved: 14/Jul/14 12:57

Description

To reproduce unpack the latest karaf-snapshot and install the JPA-feature:

feature:install jpa

and install a bundle containing a persistence-unit.

stop the JPA Container bundle.

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).

Issue Links

• duplicates: ARIES-1040 Exception during jpa-container shutdown
• is duplicated by: ARIES-1155 Error when OSGi container is stopped on aries jpa container No persistence units defined for bundle
• relates to: KARAF-2188 JPA bundle error out at shutdown