[jira] [Updated] (GEODE-4013) shutdown of a cache server with ServerLauncher causes JVM to exit before completing shutdown

2018-02-13 Thread Barbara Pruijn (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Barbara Pruijn updated GEODE-4013:
--
Fix Version/s: 1.5.0

> shutdown of a cache server with ServerLauncher causes JVM to exit before 
> completing shutdown
> 
>
> Key: GEODE-4013
> URL: https://issues.apache.org/jira/browse/GEODE-4013
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Affects Versions: 1.3.0
>Reporter: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
> Fix For: 1.5.0
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Also see GEODE-1236, concerning the same behavior with GFSH.
> A server launched via ServerLauncher is kept alive by its AcceptorImpl 
> thread.  That is the only non-daemon thread in the JVM.  If you shutdown that 
> server with ServerLauncher it will invoke cache.close() which midway through 
> closing will terminate the AcceptorImpl thread and cause the JVM to exit.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-4013) shutdown of a cache server with ServerLauncher causes JVM to exit before completing shutdown

2018-01-31 Thread ASF GitHub Bot (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated GEODE-4013:
--
Labels: pull-request-available  (was: )

> shutdown of a cache server with ServerLauncher causes JVM to exit before 
> completing shutdown
> 
>
> Key: GEODE-4013
> URL: https://issues.apache.org/jira/browse/GEODE-4013
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Affects Versions: 1.3.0
>Reporter: Bruce Schuchardt
>Priority: Major
>  Labels: pull-request-available
>
> Also see GEODE-1236, concerning the same behavior with GFSH.
> A server launched via ServerLauncher is kept alive by its AcceptorImpl 
> thread.  That is the only non-daemon thread in the JVM.  If you shutdown that 
> server with ServerLauncher it will invoke cache.close() which midway through 
> closing will terminate the AcceptorImpl thread and cause the JVM to exit.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-4013) shutdown of a cache server with ServerLauncher causes JVM to exit before completing shutdown

2017-12-05 Thread Bruce Schuchardt (JIRA)

 [ 
https://issues.apache.org/jira/browse/GEODE-4013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bruce Schuchardt updated GEODE-4013:

Affects Version/s: 1.3.0

> shutdown of a cache server with ServerLauncher causes JVM to exit before 
> completing shutdown
> 
>
> Key: GEODE-4013
> URL: https://issues.apache.org/jira/browse/GEODE-4013
> Project: Geode
>  Issue Type: Bug
>  Components: management
>Affects Versions: 1.3.0
>Reporter: Bruce Schuchardt
>
> Also see GEODE-1236, concerning the same behavior with GFSH.
> A server launched via ServerLauncher is kept alive by its AcceptorImpl 
> thread.  That is the only non-daemon thread in the JVM.  If you shutdown that 
> server with ServerLauncher it will invoke cache.close() which midway through 
> closing will terminate the AcceptorImpl thread and cause the JVM to exit.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)