You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alexander Haskell (JIRA)" <ji...@apache.org> on 2016/02/23 15:12:18 UTC
[jira] [Updated] (DIRKRB-536) KrbClient leaks sockets
[ https://issues.apache.org/jira/browse/DIRKRB-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Haskell updated DIRKRB-536:
-------------------------------------
Description: 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{noformat}{T,S}{noformat}gt() by calling release() on DefaultInternalKrbClient.transport. (was: 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.)
> KrbClient leaks sockets
> -----------------------
>
> Key: DIRKRB-536
> URL: https://issues.apache.org/jira/browse/DIRKRB-536
> Project: Directory Kerberos
> Issue Type: Bug
> Reporter: Alexander Haskell
>
> 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{noformat}{T,S}{noformat}gt() by calling release() on DefaultInternalKrbClient.transport.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)