[
https://issues.apache.org/jira/browse/DIRKRB-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15160309#comment-15160309
]
Kai Zheng commented on DIRKRB-536:
----------------------------------
Thanks Jiajia for the finding. Yeah I totally forgot the whole story. So I
guess we can't release the underlying transport as the patch does, instead, we
can add {{release}} like method to {{KrbClient}} and let it be called by the
application after ensured not to use it any more.
> 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
>
>
> 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)
