You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@knox.apache.org by "Kevin Risden (JIRA)" <ji...@apache.org> on 2018/10/03 16:17:00 UTC

[jira] [Updated] (KNOX-1505) Knox should close CuratorFramework clients when finished

     [ https://issues.apache.org/jira/browse/KNOX-1505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevin Risden updated KNOX-1505:
-------------------------------
    Attachment: KNOX-1505.patch
        Status: Patch Available  (was: In Progress)

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)