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

Posted to dev@ranger.apache.org by "Dilli Arumugam (JIRA)" <ji...@apache.org> on 2014/11/06 00:19:33 UTC

[jira] [Commented] (ARGUS-157) defensively handle potential connection leaks in LdapUserGroupBuilder

    [ https://issues.apache.org/jira/browse/ARGUS-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14199331#comment-14199331 ] 

Dilli Arumugam commented on ARGUS-157:
--------------------------------------

commit cherry picked and pushed to 0.4 branch

> defensively handle potential connection leaks in  LdapUserGroupBuilder
> ----------------------------------------------------------------------
>
>                 Key: ARGUS-157
>                 URL: https://issues.apache.org/jira/browse/ARGUS-157
>             Project: Argus
>          Issue Type: Improvement
>    Affects Versions: 0.4.0
>            Reporter: Dilli Arumugam
>            Assignee: Dilli Arumugam
>             Fix For: 0.4.0
>
>         Attachments: ARGUS-157.patch
>
>
> It is likely KnoxLdapConnection could leak connections if there are exceptions thrown from with code calling ldap.
> We should close the searchResultEnum in finally block to avoid potential ldap connection leak.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)