directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Haskell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DIRKRB-536) KrbClient leaks sockets
Date Wed, 24 Feb 2016 20:19:18 GMT

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

Alexander Haskell updated DIRKRB-536:
-------------------------------------
    Attachment: reuse_client.patch

This should work much better. Connections are created and closed per request. I've tried it
out in our own project and it works.

This has the advantage that there is no way for a user of the client to forget to call close()
or release(). Does this look good to you?

> KrbClient leaks sockets
> -----------------------
>
>                 Key: DIRKRB-536
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-536
>             Project: Directory Kerberos
>          Issue Type: Bug
>            Reporter: Alexander Haskell
>            Assignee: Alexander Haskell
>         Attachments: release_socket.patch, reuse_client.patch
>
>
> KrbClient does not close sockets at the end of a request. This is not a problem for KinitTool
as the jvm closes the sockets at program termination. A longer running application has to
rely on the garbage collector cleaning up open sockets. The most likely location to do this
appears to be at the end of DefaultInternalKrbClient.doRequest\{T,S}gt() by calling release()
on DefaultInternalKrbClient.transport.



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

Mime
View raw message