You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/09/09 06:06:00 UTC
[jira] [Commented] (GEODE-10336) ConnectionTable.close does not null out its static lastInstance field
[ https://issues.apache.org/jira/browse/GEODE-10336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602139#comment-17602139 ]
ASF subversion and git services commented on GEODE-10336:
---------------------------------------------------------
Commit c4ab763dea39328ba276e8c527bf531050f20cde in geode's branch refs/heads/develop from Mario Ivanac
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c4ab763dea ]
GEODE-10336: set lastInstance to null (#7843)
* GEODE-10336: set lastInstance to null
* GEODE-10336: added test
> ConnectionTable.close does not null out its static lastInstance field
> ---------------------------------------------------------------------
>
> Key: GEODE-10336
> URL: https://issues.apache.org/jira/browse/GEODE-10336
> Project: Geode
> Issue Type: Bug
> Components: membership
> Reporter: Darrel Schneider
> Assignee: Mario Ivanac
> Priority: Major
> Labels: blocks-1.16.0, pull-request-available
>
> The ConnectionTable.close method does a bunch of work but it does not null out the static "lastInstance" atomic. This causes it to keep the ConnectionTable alive which ends up keeping the InternalDistributedSystem alive.
> The easiest fix is to do this at the end of close: "emergencyClose();". The emergencyClose correctly set the lastInstance atomic to null.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)