You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2016/02/12 06:04:18 UTC
[jira] [Reopened] (GEODE-857) SystemFailure.stopWatchdog will
always wait 1 second
[ https://issues.apache.org/jira/browse/GEODE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anthony Baker reopened GEODE-857:
---------------------------------
I ran into a failure with this unit test:
{code:java}
com.gemstone.gemfire.SystemFailureJUnitTest > testStopThreads FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertTrue(Assert.java:52)
at com.gemstone.gemfire.SystemFailureJUnitTest.testStopThreads(SystemFailureJUnitTest.java:51)
{code}
> SystemFailure.stopWatchdog will always wait 1 second
> ----------------------------------------------------
>
> Key: GEODE-857
> URL: https://issues.apache.org/jira/browse/GEODE-857
> Project: Geode
> Issue Type: Bug
> Reporter: Dan Smith
> Assignee: Dan Smith
> Fix For: 1.0.0-incubating.M2
>
>
> This method is called during distributed system shutdown. It synchronizes on failureSync, and then calls Thread.join on the watchDog thread and waits one second.
> The watchDog thread can't wake up until it can get the failureSync, so the Thread.join call will always end up waiting.
> This adds a lot of time to our tests, because we often disconnect the distributed system.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)