[
https://issues.apache.org/jira/browse/GEODE-7089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916852#comment-16916852
]
ASF subversion and git services commented on GEODE-7089:
--------------------------------------------------------
Commit 920723c5b56b9c00ccb2366adb5e4ba0f0f06927 in geode's branch
refs/heads/release/1.10.0 from Ryan McMahon
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=920723c ]
GEODE-7089: Each client registration thread uses its own queue (#3976)
Co-authored-by: Ryan McMahon <[email protected]>
Co-authored-by: Donal Evans <[email protected]>
(cherry picked from commit 5d0153ad4adb1612a1083673f98b1982819a6589)
> Possible memory leak due to failure to clean up client's registration queue
> ---------------------------------------------------------------------------
>
> Key: GEODE-7089
> URL: https://issues.apache.org/jira/browse/GEODE-7089
> Project: Geode
> Issue Type: Bug
> Components: client queues
> Reporter: Ryan McMahon
> Assignee: Ryan McMahon
> Priority: Major
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> It is possible for a client's queue to leak and never be removed from the
> ClientRegistrationEventQueueManager's collection, which will result in it
> collecting events indefinitely and ultimately cause an OOM exception. This
> can happen if the registration fails for any reason (GII failed due to a peer
> crashing, unforseen serialization issues while copying the queue, etc). If
> the client does not retry on the same server after failure, the queue will
> leak. This is because we currently only remove the queue once a successful
> registration is performed, but its possible the client will just go to a
> different server on its next attempt.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
