You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Sai Boorlagadda (JIRA)" <ji...@apache.org> on 2018/09/27 20:03:00 UTC
[jira] [Commented] (GEODE-5787) Support graceful bouncing DUnit VMs
on windows
[ https://issues.apache.org/jira/browse/GEODE-5787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630973#comment-16630973 ]
Sai Boorlagadda commented on GEODE-5787:
----------------------------------------
There is no easy hack implement the new way unless to refactor the existing dunit framework.
> 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: 20m
> 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)