Thanks for the workaround, Bela! <br>I've included it in <a href="https://github.com/infinispan/infinispan/pull/1358">https://github.com/infinispan/infinispan/pull/1358</a>.<br><br><br><div class="gmail_quote">On Wed, Oct 3, 2012 at 9:32 AM, Bela Ban <span dir="ltr"><<a href="mailto:bban@redhat.com" target="_blank">bban@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
<br>
On 10/2/12 6:02 PM, Dan Berindei wrote:<br>
<br>
>> The members should be updated in viewAccepted(). When you connect a<br>
>> channel, then viewAccepted() will be called *before* JChannel.connect()<br>
>> returns, so the main thread won't have a chance of accessing members<br>
>> before that.<br>
>><br>
>><br>
> Ok, if viewAccepted() is guaranteed to be called before connect() returns<br>
> then you're right, the latch is superfluous. We only need to call<br>
> viewAccepted() ourselves if the channel was injected (which we already do).<br>
><br>
> In this particular case, however, we don't get a viewAccepted() call or an<br>
> exception from connect(), so I'm not sure it would have been better (easier<br>
> to debug) without the latch.<br>
<br>
<br>
</div>This is due to <a href="https://issues.jboss.org/browse/JGRP-1522" target="_blank">https://issues.jboss.org/browse/JGRP-1522</a>, which was<br>
introduced in 3.2.0; when this is fixed, you will get a viewAccepted().<br>
The workaround is to set NAKACK{2}.become_server_queue_size=0.<br>
<div><div><br>
--<br>
Bela Ban, JGroups lead (<a href="http://www.jgroups.org" target="_blank">http://www.jgroups.org</a>)<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</div></div></blockquote></div><br>