[
https://issues.apache.org/jira/browse/KNOX-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637133#comment-16637133
]
Kevin Risden edited comment on KNOX-1505 at 10/3/18 4:16 PM:
-------------------------------------------------------------
Patch that does the following:
* Uses try-with-resources where possible
* Uses blockUntilConnected to ensure we connect before trying to work with
Zookeeper
* Ensure that clientService closes each of the clients it is responsible for
was (Author: risdenk):
Patch that does the following:
* Uses try-with-resources where possible
* Uses blockUntilConnected to ensure we connect before trying to work with
Zookeeper
* Ensure that clientService is closed as well at the end
> Knox should close CuratorFramework clients when finished
> --------------------------------------------------------
>
> Key: KNOX-1505
> URL: https://issues.apache.org/jira/browse/KNOX-1505
> Project: Apache Knox
> Issue Type: Bug
> Reporter: Kevin Risden
> Assignee: Kevin Risden
> Priority: Major
> Fix For: 1.2.0
>
> Attachments: KNOX-1505.patch
>
>
> While looking at KNOX-1488, found that the CuratorFramework clients are not
> always closed. This can cause resource leaks like a StackOverflow.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
