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/08 06:11:00 UTC

[jira] [Commented] (GEODE-10335) TXManagerImpl.close does not remove itself from the static singeton

    [ https://issues.apache.org/jira/browse/GEODE-10335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17601647#comment-17601647 ] 

ASF subversion and git services commented on GEODE-10335:
---------------------------------------------------------

Commit d73bcd9a2aa0eeb94fad0e9d225a87b9af024000 in geode's branch refs/heads/develop from Mario Ivanac
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d73bcd9a2a ]

GEODE-10335: TXManagerImpl.close resets currentInstance (#7844)

* GEODE-10335: TXManagerImpl.close resets currentInstance

* GEODE-10335: added test

> TXManagerImpl.close does not remove itself from the static singeton
> -------------------------------------------------------------------
>
>                 Key: GEODE-10335
>                 URL: https://issues.apache.org/jira/browse/GEODE-10335
>             Project: Geode
>          Issue Type: Bug
>          Components: transactions
>            Reporter: Darrel Schneider
>            Assignee: Mario Ivanac
>            Priority: Major
>              Labels: blocks-1.16.0, pull-request-available
>
> TXManagerImpl.close does not remove itself from the static singleton. This causes it to keep the GemFireCacheImpl alive after it has been closed.
> The simple fix is to add "currentInstance = null" at the end of the close method.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)