[ https://issues.apache.org/jira/browse/GEODE-2497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876992#comment-15876992 ]
ASF subversion and git services commented on GEODE-2497: -------------------------------------------------------- Commit a6dfa4ca630a82fcf92942a834f8255e86d2bfcb in geode's branch refs/heads/feature/GEODE-2497 from [~bschuchardt] [ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=a6dfa4c ] GEODE-2497 surprise members are never timed out during startup Moved the creation of the timer to GMSMembershipManager.started() Removed write-lock in timer-creation method since it's only called from one place now Altered the way that the timer-creation method finds the InternalDistributedSystem. The old way of using getAnyInstance() was the primary source of the problem since it returns null until startup is completed. Altered the surprise-member unit test to ensure that it's using the timer and not relying on installation of a new membership view to clean things up. Altered the surprise-member unit test to run faster. It now completes in under 10 seconds. > surprise members are never timed out during startup > --------------------------------------------------- > > Key: GEODE-2497 > URL: https://issues.apache.org/jira/browse/GEODE-2497 > Project: Geode > Issue Type: Bug > Components: membership > Reporter: Bruce Schuchardt > Assignee: Bruce Schuchardt > > A system was observed to hang during startup when a "surprise member" was > added but then never timed out. The system hung waiting for a response to a > startup message sent to the surprise member. -- This message was sent by Atlassian JIRA (v6.3.15#6346)