[
https://issues.apache.org/jira/browse/CURATOR-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zealot updated CURATOR-437:
---------------------------
Attachment: curator.log
> zookeeper connection leak when session expires.
> -----------------------------------------------
>
> Key: CURATOR-437
> URL: https://issues.apache.org/jira/browse/CURATOR-437
> Project: Apache Curator
> Issue Type: Bug
> Components: Client
> Affects Versions: 4.0.0
> Reporter: zealot
> Attachments: curator.log
>
>
> https://github.com/apache/curator/blob/master/curator-client/src/main/java/org/apache/curator/utils/InjectSessionExpiration.java#L97
> Curator inject will set zookeeper state to CLOSED when session expires
> without close zk associated threads.
> If state set to CLOSED, ZooKeeper.close() function won't be able to release
> resources properly, which lead to memory and connection leak.
> To reproduce, create a curator client, then shutdown zk server, wait for
> session timeout, restart the zk server. There will be two ZooKeeper instances
> and two connections to the server.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
