Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
Date: Thu, 20 Dec 2012 11:43:07 -0800
Message-ID: 
 <CAKMXxZNzwbha59dXYKC_wdqnJaF8ZqEvwF3=WDQKis2nmh+V4Q@mail.gmail.com>
Subject: Deadlock on install/refresh
From: Jad Naous <jad@nerati.com>
To: dev@felix.apache.org
Content-Type: multipart/alternative; boundary=14dae93404b9a7b0be04d14df05a

--14dae93404b9a7b0be04d14df05a
Content-Type: text/plain; charset=ISO-8859-1

I am using Gemini JPA along with EclipseLink on Apache Felix, and I can
reproduce a deadlock at will. Here's what happens:

- Gemini JPA gets installed.
- My bundle which includes persistence entities is installing.
- Gemini JPA gets notification about my bundle's status change
- Gemini JPA scans the bundle, decides it's a persistence bundle, then
calls refresh on the bundle.
- The refresh is locked waiting for the install to complete
- The install is waiting for the refresh to complete.

Anybody seen something like that happen before? What's the right way to do
this? It seems like a lock ordering problem (looking at what's being
locked, it seems one thread is waiting for the bundle lock while the other
is waiting for the global lock).

Thanks,

Jad.

--14dae93404b9a7b0be04d14df05a--