felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jad Naous <...@nerati.com>
Subject Re: IPOJO initialization + refresh deadlock
Date Mon, 07 Jan 2013 13:10:42 GMT
To close the loop on this thread, I've created
FELIX-3839<https://issues.apache.org/jira/browse/FELIX-3839>


On Thu, Jan 3, 2013 at 2:26 AM, Bertrand Delacretaz
<bdelacretaz@apache.org>wrote:

> On Thu, Jan 3, 2013 at 10:19 AM, Jad Naous <jad@nerati.com> wrote:
> > On Thu, Jan 3, 2013 at 12:55 AM, Bertrand Delacretaz <
> bdelacretaz@apache.org
> >>... I haven't studied your case in detail but you might want to compare
> >> with FELIX-3067...
>
> > Seems related. I'm guessing you are running into the deadlock because the
> > classloader tries to acquire the global lock while holding some
> application
> > lock?
>
> I cannot say for sure, haven't looked at that issue in a while. The
> SCR subsystem might have its own locks that contribute to exposing the
> deadlocks.
>
> >
> > I'm not familiar with the Sling Launchpad. Is this a maven repo somewhere
> > where I can get your patches?...
>
> You can build Sling and use its launchpad as described in FELIX-3067
> if you want, but the key part in reproducing the deadlocks is the
> stress tests [1] - I used Sling only as a provider of several bundles
> which use SCR services, as that helps expose the problem.
>
> -Bertrand
>
> [1] https://github.com/bdelacretaz/osgi-stresser
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message