[ https://issues.apache.org/jira/browse/GEODE-5361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nabarun updated GEODE-5361: --------------------------- Fix Version/s: (was: 1.8.0) 1.7.0 > CacheServer is not restarted for force disconnected/reconnected servers > ----------------------------------------------------------------------- > > Key: GEODE-5361 > URL: https://issues.apache.org/jira/browse/GEODE-5361 > Project: Geode > Issue Type: Task > Components: tests > Reporter: Helena Bales > Priority: Major > Labels: pull-request-available > Fix For: 1.7.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Servers started via the ClusterStartupRule and disconnected and reconnected > through that rule may not have a CacheServer MBean following the reconnect. > This indicates that either the CacheServer is recreated automatically when a > server is crashed and the "waitTilServerFullyReconnected" method does not > wait long enough for it to be recreated, OR the CacheServer is not recreated > automatically following a restart. The intermittent nature of this failure > points to the former. > > The test that failed for this reason is > JMXMBeanReconnectDUnitTest#testRemoteBeanKnowledge_MaintainLocatorAndCrashServer > See the failure > [here|http://files.apachegeode-ci.info/builds/1.8.0-build.1086/test-results/distributedTest/1530134986/classes/org.apache.geode.management.JMXMBeanReconnectDUnitTest.html#testRemoteBeanKnowledge_MaintainLocatorAndCrashServer] -- This message was sent by Atlassian JIRA (v7.6.3#76005)