Hi,
I started to see that too yesterday and now I also see it in MultipleNodesLeavingTest but it is rarely reproducible.
The state transfer never ends because a provider sends all segments requested by a consumer but apparently some messages are delayed in transit and the consumer only 'sees' a partial set.  The rebalance is not confirmed by this node and it times out.
I'm still investigating this.

Cheers

On 10/02/2012 06:06 PM, Sanne Grinovero wrote:
I just updated my local copy of Infinispan and this is the result in
the Query testsuite:

Failed tests:
testIndexingWorkDistribution(org.infinispan.query.distributed.MultiNodeDistributedTest):
expected:<5> but was:<4>
Tests run: 128, Failures: 1, Errors: 0, Skipped: 0

OR:

Failed tests:
testIndexingWorkDistribution(org.infinispan.query.distributed.MultiNodeDistributedTest):
expected:<5> but was:<4>
  testQueryAfterAddingNewNode(org.infinispan.query.statetransfer.StateTransferQueryDistributedIndexTest):
org.infinispan.CacheException: Unable to invoke method public void
org.infinispan.statetransfer.StateTransferManagerImpl.waitForInitialStateTransferToComplete()
throws java.lang.InterruptedException on object of type
StateTransferManagerImpl
Tests run: 128, Failures: 2, Errors: 0, Skipped: 0

It doesn't fail all the time, but almost every time. It passed the
testsuite once, and it timeouts initial state transfer very often
(attached thread dump)

Doesn't look like NBST is non blocking after all?

Specifically I've been testing commit bee1a0a



_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev