IPOJO initialization + refresh deadlock

If a bundle undergoes a refresh while ipojo is still initializing components, a deadlock can happen. The issue is that if ipojo is attempting to register a service, it will be doing it while synchronizing on the InstanceCreator instance. It will then try to register a service which requires the fr

Re: IPOJO initialization + refresh deadlock

On 12/20/12 4:10 PM, Jad Naous wrote: If a bundle undergoes a refresh while ipojo is still initializing components, a deadlock can happen. The issue is that if ipojo is attempting to register a service, it will be doing it while synchronizing on the InstanceCreator instance. It will then try to

Re: IPOJO initialization + refresh deadlock

It does look like the same issue. Got the trunk/framework. mvn clean install gives: [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ org.apache.felix.framework --- Dec 20, 2012 3:54:59 PM org.sonatype.guice.bean.reflect.Logs$JULSink warn WARNING: Error injecting: org.apache.mave

Re: IPOJO initialization + refresh deadlock

On 12/20/12 6:56 PM, Jad Naous wrote: It does look like the same issue. Got the trunk/framework. mvn clean install gives: [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ org.apache.felix.framework --- Dec 20, 2012 3:54:59 PM org.sonatype.guice.bean.reflect.Logs$JULSink warn W

Re: IPOJO initialization + refresh deadlock

It built fine for me. I'm was building with Java 7. Regardless, I deployed snapshots of framework, main, and main.distribution, so just grab what you want from the Apache snapshot repo to try it out. -> richard On 12/20/12 18:56 , Jad Naous wrote: It does look like the same issue. Got the

Re: IPOJO initialization + refresh deadlock

Thanks! I was building with java6. Don't know if that is the issue. Anyway, I tested the snapshot, and looks like that fixes it. Any idea when 4.1.0 will be released? Do you know if http://svn.apache.org/viewvc?view=revision&revision=1421958 will apply cleanly onto 4.0.3? Otherwise, how stable do

Re: IPOJO initialization + refresh deadlock

On 12/22/12 20:41 , Jad Naous wrote: Thanks! I was building with java6. Don't know if that is the issue. Anyway, I tested the snapshot, and looks like that fixes it. Any idea when 4.1.0 will be released? Do you know if http://svn.apache.org/viewvc?view=revision&revision=1421958 will apply cleanl

Re: IPOJO initialization + refresh deadlock

Happy new year! I'm running into another deadlock now. It seems like there needs to be a more rigorous study of how locking is used in the framework. In particular, it seems like the framework should not be invoking any listeners within the same thread that's executing the stopping/starting/refres

Re: IPOJO initialization + refresh deadlock

On 1/1/13 06:09, Jad Naous wrote: Happy new year! I'm running into another deadlock now. It seems like there needs to be a more rigorous study of how locking is used in the framework. In particular, it seems like the framework should not be invoking any listeners within the same thread that's ex

Re: IPOJO initialization + refresh deadlock

On Tue, Jan 1, 2013 at 6:21 AM, Richard S. Hall wrote: > On 1/1/13 06:09, Jad Naous wrote: > >> Happy new year! >> >> I'm running into another deadlock now. It seems like there needs to be a >> more rigorous study of how locking is used in the framework. In >> particular, >> it seems like the fram

Re: IPOJO initialization + refresh deadlock

On 1/1/13 10:37, Jad Naous wrote: On Tue, Jan 1, 2013 at 6:21 AM, Richard S. Hallwrote: On 1/1/13 06:09, Jad Naous wrote: Happy new year! I'm running into another deadlock now. It seems like there needs to be a more rigorous study of how locking is used in the framework. In particular, it se

Re: IPOJO initialization + refresh deadlock

On Tue, Jan 1, 2013 at 7:58 AM, Richard S. Hall wrote: > On 1/1/13 10:37, Jad Naous wrote: > >> On Tue, Jan 1, 2013 at 6:21 AM, Richard S. Hall** >> wrote: >> >> On 1/1/13 06:09, Jad Naous wrote: >>> >>> Happy new year! I'm running into another deadlock now. It seems like there needs t

Re: IPOJO initialization + refresh deadlock

On 1/1/13 11:13, Jad Naous wrote: On Tue, Jan 1, 2013 at 7:58 AM, Richard S. Hall wrote: On 1/1/13 10:37, Jad Naous wrote: On Tue, Jan 1, 2013 at 6:21 AM, Richard S. Hall** wrote: On 1/1/13 06:09, Jad Naous wrote: Happy new year! I'm running into another deadlock now. It seems like the

Re: IPOJO initialization + refresh deadlock

On Tue, Jan 1, 2013 at 8:30 AM, Richard S. Hall wrote: > On 1/1/13 11:13, Jad Naous wrote: > >> On Tue, Jan 1, 2013 at 7:58 AM, Richard S. Hall > >wrote: >> >> On 1/1/13 10:37, Jad Naous wrote: >>> >>> On Tue, Jan 1, 2013 at 6:21 AM, Richard S. Hall** wrote: On 1/1/13 06:09

Re: IPOJO initialization + refresh deadlock

On 1/1/13 11:51, Jad Naous wrote: On Tue, Jan 1, 2013 at 8:30 AM, Richard S. Hall wrote: On 1/1/13 11:13, Jad Naous wrote: On Tue, Jan 1, 2013 at 7:58 AM, Richard S. Hall wrote: On 1/1/13 10:37, Jad Naous wrote: On Tue, Jan 1, 2013 at 6:21 AM, Richard S. Hall** wrote: On 1/1/13 0

Re: IPOJO initialization + refresh deadlock

On Tue, Jan 1, 2013 at 9:16 AM, Richard S. Hall wrote: > > On 1/1/13 11:51, Jad Naous wrote: > >> On Tue, Jan 1, 2013 at 8:30 AM, Richard S. Hall > >wrote: >> >> On 1/1/13 11:13, Jad Naous wrote: >>> >>> On Tue, Jan 1, 2013 at 7:58 AM, Richard S. Hall >>> > wrote: > On 1/1/13 10:3

Re: IPOJO initialization + refresh deadlock

On 1/1/13 12:40, Jad Naous wrote: On Tue, Jan 1, 2013 at 9:16 AM, Richard S. Hall wrote: On 1/1/13 11:51, Jad Naous wrote: On Tue, Jan 1, 2013 at 8:30 AM, Richard S. Hall wrote: On 1/1/13 11:13, Jad Naous wrote: On Tue, Jan 1, 2013 at 7:58 AM, Richard S. Hall wrote: On 1/1/13 10:

Re: IPOJO initialization + refresh deadlock

On Tue, Jan 1, 2013 at 9:58 AM, Richard S. Hall wrote: > On 1/1/13 12:40, Jad Naous wrote: > >> On Tue, Jan 1, 2013 at 9:16 AM, Richard S. Hall > >wrote: >> >> On 1/1/13 11:51, Jad Naous wrote: >>> >>> On Tue, Jan 1, 2013 at 8:30 AM, Richard S. Hall >>> > wrote: > On 1/1/13 11:13,

Re: IPOJO initialization + refresh deadlock

On 1/1/13 13:14, Jad Naous wrote: On Tue, Jan 1, 2013 at 9:58 AM, Richard S. Hall wrote: On 1/1/13 12:40, Jad Naous wrote: On Tue, Jan 1, 2013 at 9:16 AM, Richard S. Hall wrote: On 1/1/13 11:51, Jad Naous wrote: On Tue, Jan 1, 2013 at 8:30 AM, Richard S. Hall wrote: On 1/1/13 11

Re: IPOJO initialization + refresh deadlock

Hi, On Tue, Jan 1, 2013 at 12:09 PM, Jad Naous wrote: > ...I'm running into another deadlock now. It seems like there needs to be a > more rigorous study of how locking is used in the framework. In particular, > it seems like the framework should not be invoking any listeners within the > same th

Re: IPOJO initialization + refresh deadlock

On Thu, Jan 3, 2013 at 12:55 AM, Bertrand Delacretaz wrote: > Hi, > > On Tue, Jan 1, 2013 at 12:09 PM, Jad Naous wrote: > > ...I'm running into another deadlock now. It seems like there needs to > be a > > more rigorous study of how locking is used in the framework. In > particular, > > it seems

Re: IPOJO initialization + refresh deadlock

On Thu, Jan 3, 2013 at 10:19 AM, Jad Naous wrote: > On Thu, Jan 3, 2013 at 12:55 AM, Bertrand Delacretaz >... 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 t

Re: IPOJO initialization + refresh deadlock

To close the loop on this thread, I've created FELIX-3839 On Thu, Jan 3, 2013 at 2:26 AM, Bertrand Delacretaz wrote: > On Thu, Jan 3, 2013 at 10:19 AM, Jad Naous wrote: > > On Thu, Jan 3, 2013 at 12:55 AM, Bertrand Delacretaz < > bdelacre...@apa