[
https://issues.apache.org/jira/browse/GEODE-3079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Galen O'Sullivan updated GEODE-3079:
------------------------------------
Description:
Implement at least the {{terminateNow()}}, {{emergencyClose()}}, and
{{cleanup()}} methods (and do a check for others) on
{{NewClientServerConnection}}. Make sure that we handle each one in a similar
fashion to how the legacy {{ServerConnection}} does.
AcceptorImpl and its callers use loadEmergencyClasses() to make sure that
classes which are needed for a proper shutdown are loaded when the Cache
starts, and prior to shutdown (which could be an OOM or similar situation).
In the parent call (I think AcceptorImpl) add a call to our own method, and
call the same method on any classes we depend on.
was:Implement at least the {{terminateNow()}}, {{emergencyClose()}}, and
{{cleanup()}} methods (and do a check for others) on
{{NewClientServerConnection}}. Make sure that we handle each one in a similar
fashion to how the legacy {{ServerConnection}} does.
> Write shutdown handlers for NewClientServerConnection
> -----------------------------------------------------
>
> Key: GEODE-3079
> URL: https://issues.apache.org/jira/browse/GEODE-3079
> Project: Geode
> Issue Type: Sub-task
> Components: client/server
> Reporter: Galen O'Sullivan
>
> Implement at least the {{terminateNow()}}, {{emergencyClose()}}, and
> {{cleanup()}} methods (and do a check for others) on
> {{NewClientServerConnection}}. Make sure that we handle each one in a similar
> fashion to how the legacy {{ServerConnection}} does.
> AcceptorImpl and its callers use loadEmergencyClasses() to make sure that
> classes which are needed for a proper shutdown are loaded when the Cache
> starts, and prior to shutdown (which could be an OOM or similar situation).
> In the parent call (I think AcceptorImpl) add a call to our own method, and
> call the same method on any classes we depend on.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
