You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Bruce Schuchardt (JIRA)" <ji...@apache.org> on 2016/04/07 19:30:26 UTC
[jira] [Resolved] (GEODE-1187) If a server launched by Gfsh goes
into auto-reconnect the server's PID file is deleted
[ https://issues.apache.org/jira/browse/GEODE-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Schuchardt resolved GEODE-1187.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0-incubating.M2
> If a server launched by Gfsh goes into auto-reconnect the server's PID file is deleted
> --------------------------------------------------------------------------------------
>
> Key: GEODE-1187
> URL: https://issues.apache.org/jira/browse/GEODE-1187
> Project: Geode
> Issue Type: Bug
> Components: gfsh
> Reporter: Bruce Schuchardt
> Assignee: Bruce Schuchardt
> Fix For: 1.0.0-incubating.M2
>
>
> If a server launched by gfsh is kicked out of the distributed system and goes into auto-reconnect its process-ID file will disappear. This can cause monitoring programs to think that the process has failed and initiate creation of a new process.
> The problem seems to be that the gfsh ServerLauncher class has no checks for a reconnecting server. The launcher stops and deletes the PID file but the Reconnect thread and, subsequently, the Acceptor thread for the cache server keep the JVM from exiting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)