[infinispan-issues] [JBoss JIRA] (ISPN-3304) ClusterTopologyManagerTest.testClusterRecoveryAfterThreeWaySplit fails randomly

[Pedro Ruivo (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-3304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pedro Ruivo updated ISPN-3304:
------------------------------

    Attachment: ClusterTopologyManagerTest.testClusterRecoveryAfterThreeWaySplit.tar.gz


attached trace logs. The tar contains two log files with the same error but in different executions. 
                
> ClusterTopologyManagerTest.testClusterRecoveryAfterThreeWaySplit fails randomly
> -------------------------------------------------------------------------------
>
>                 Key: ISPN-3304
>                 URL: https://issues.jboss.org/browse/ISPN-3304
>             Project: Infinispan
>          Issue Type: Bug
>    Affects Versions: 5.3.0.Final
>            Reporter: Pedro Ruivo
>            Assignee: Mircea Markus
>             Fix For: 6.0.0.Final
>
>         Attachments: ClusterTopologyManagerTest.testClusterRecoveryAfterThreeWaySplit.tar.gz
>
>
> {code:java}
> java.lang.RuntimeException: Timed out before caches had complete views.  Expected 3 members in each view.  Views are as follows: [[ClusterTopologyManagerTest-NodeL-25341], [ClusterTopologyManagerTest-NodeN-52944, ClusterTopologyManagerTest-NodeM-9914], [ClusterTopologyManagerTest-NodeN-52944, ClusterTopologyManagerTest-NodeM-9914]]
>         at org.infinispan.test.TestingUtil.viewsTimedOut(TestingUtil.java:232)
>         at org.infinispan.test.TestingUtil.viewsTimedOut(TestingUtil.java:222)
>         at org.infinispan.test.TestingUtil.blockUntilViewsReceived(TestingUtil.java:214)
>         at org.infinispan.test.TestingUtil.blockUntilViewsReceived(TestingUtil.java:255)
>         at org.infinispan.statetransfer.ClusterTopologyManagerTest.testClusterRecoveryAfterThreeWaySplit(ClusterTopologyManagerTest.java:156)
>         ...
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira