[
https://issues.apache.org/jira/browse/GEODE-3314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111328#comment-16111328
]
ASF subversion and git services commented on GEODE-3314:
--------------------------------------------------------
Commit d91096c19a453e3d04f9b3d9151ad57dc8e79e0a in geode's branch
refs/heads/develop from [~gosullivan]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=d91096c ]
GEODE-3314: Fix DLockService token leak.
And add a test so that we don't do that again.
We had been unlocking the DLock on the remote server before freeing the
local `DLockToken`. This meant that the local token got reused by
another thread acquiring the same lock and the count went up and up and
up (due to some logic that wouldn't decrease the count if it no longer
owned the token).
Tokens should no longer have usageCounts that climb over time, which
means they should be released normally by freeResources.
Signed-off-by: Bruce Schuchardt <[email protected]>
Signed-off-by: Galen O'Sullivan <[email protected]>
This closes #663
Signed-off-by: Hitesh Khamesra <[email protected]>
> OldGen heap usage grows without increase in data size, large number of
> DLockTokens
> ----------------------------------------------------------------------------------
>
> Key: GEODE-3314
> URL: https://issues.apache.org/jira/browse/GEODE-3314
> Project: Geode
> Issue Type: Bug
> Components: distributed lock service
> Reporter: Udo Kohlmeyer
> Assignee: Udo Kohlmeyer
>
> When using Global Replicate regions, the DLockTokens are not correctly
> cleaned up, causing a memory leak.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
