[
https://issues.apache.org/jira/browse/GEODE-5787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16656027#comment-16656027
]
ASF subversion and git services commented on GEODE-5787:
--------------------------------------------------------
Commit 730e30092f689ea81a5419dd40c653c12cd16569 in geode's branch
refs/heads/feature/GEODE-5787-dunit-internal from Sai Boorlagadda
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=730e300 ]
Merge branch 'develop' into feature/GEODE-5787-dunit-internal
> Support graceful bouncing DUnit VMs on windows
> ----------------------------------------------
>
> Key: GEODE-5787
> URL: https://issues.apache.org/jira/browse/GEODE-5787
> Project: Geode
> Issue Type: New Feature
> Components: tests
> Reporter: Sai Boorlagadda
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Process.destroy is not graceful on windows and causes distributed system to
> get into suspect processing and network partition when used in DUnit to
> restart VMs.
> There were existing JDK
> [bugs|https://bugs.openjdk.java.net/browse/JDK-8056139] open requesting for
> supporting graceful destroy for Windows.
> Underlying native implementation on Linux can take advantage of SIGTERM vs
> SIGKILL and JDK support process.destroy and process.destroyForcibly, where as
> on Windows this differentiation is not possible so its unlikely that we will
> see JDK support for graceful destroy.
> A better approach would be to invoke 'System.exit( n )' using VM.invoke.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
