You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/04/02 05:50:41 UTC

[jira] [Commented] (THRIFT-3088) TThreadPoolServer with Sasl auth may leak CLOSE_WAIT socket

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

ASF GitHub Bot commented on THRIFT-3088:
----------------------------------------

Github user jeking3 commented on the issue:

    https://github.com/apache/thrift/pull/432
  
    @jfarrell this can be closed - it was fixed a while back.


> TThreadPoolServer with Sasl auth may leak CLOSE_WAIT socket
> -----------------------------------------------------------
>
>                 Key: THRIFT-3088
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3088
>             Project: Thrift
>          Issue Type: Bug
>          Components: Java - Library
>    Affects Versions: 0.9
>            Reporter: Winger Pun
>             Fix For: 0.9.3
>
>
> Start TThreadPoolServer to server with TSaslServerTransport.Factory as transportFactory. While using nc to test the specified port whether reachable, it will leak CLOSE_WAIT socket.That's because nc will close socket at once while successful connect TThreadPoolServer, but the server still try using sasl protocol to build an inputTransport which of course failed at once. However inputTransport is null which makes it can't close socket properly which lead to CLOSE_WAIT socket.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)