You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by GitBox <gi...@apache.org> on 2021/05/15 04:36:51 UTC

[GitHub] [zeppelin] zjffdu commented on pull request #4119: [ZEPPELIN-5372]. Fix the problem of Ldap connection leak in LdapGroupRealm

zjffdu commented on pull request #4119:
URL: https://github.com/apache/zeppelin/pull/4119#issuecomment-841598895


   Not sure whether this is the root cause. According the javadoc of Context#close, it looks like even close is not called, it would be released. 
   
   ```
       /**
        * Closes this context.
        * This method releases this context's resources immediately, instead of
        * waiting for them to be released automatically by the garbage collector.
        *
        * <p> This method is idempotent:  invoking it on a context that has
        * already been closed has no effect.  Invoking any other method
        * on a closed context is not allowed, and results in undefined behaviour.
        *
        * @throws  NamingException if a naming exception is encountered
        */
       public void close() throws NamingException;
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org