[infinispan-issues] [JBoss JIRA] (ISPN-2503) Re-enable FD_SOCK in the test suite

[Dan Berindei (JIRA)]

Dan Berindei created ISPN-2503:
----------------------------------

             Summary: Re-enable FD_SOCK in the test suite
                 Key: ISPN-2503
                 URL: https://issues.jboss.org/browse/ISPN-2503
             Project: Infinispan
          Issue Type: Bug
          Components: Test Suite
    Affects Versions: 5.2.0.Beta3
            Reporter: Dan Berindei
            Assignee: Dan Berindei
            Priority: Critical
             Fix For: 5.2.0.Final


Some tests fail randomly with a timeout waiting for a new view after stopping the coordinator:

{noformat}
01:08:11,695 ERROR (testng-CacheClusterJoinTest:) [UnitTestTestNGListener] Test testIsCoordinator(org.infinispan.api.CacheClusterJoinTest) failed.
java.lang.RuntimeException: Timed out before caches had complete views.  Expected 1 members in each view.  Views are as follows: [[NodeC-27739, NodeD-5092]]
	at org.infinispan.test.TestingUtil.viewsTimedOut(TestingUtil.java:249)
	at org.infinispan.test.TestingUtil.blockUntilViewsReceived(TestingUtil.java:311)
	at org.infinispan.api.CacheClusterJoinTest.testIsCoordinator(CacheClusterJoinTest.java:87)
{noformat}


This happens because the old coordinator tries to install a new view without it before stopping, but fails:

{noformat}
01:07:21,616 WARN  (ViewHandler,ISPN,NodeC-27739:) [GMS] NodeC-27739: failed to collect all ACKs (expected=1) for view [NodeD-5092|2] after 2000ms, missing ACKs from [NodeD-5092]
{noformat}

The survivor never received the view installation message, so it didn't install view {{[NodeD-5092|2]}}. Because it didn't have any failure detection, it couldn't realize that the current coordinator was dead so it never installed a new view.

It's not clear why the survivor didn't receive the view message at all in the test suite, but this can obviously happen so we should enable FD_SOCK in the test suite.

--
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