You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "James E. King, III (JIRA)" <ji...@apache.org> on 2016/04/04 22:31:25 UTC
[jira] [Commented] (THRIFT-3753) TServerFramework::stop may fail to
interrupt connected clients
[ https://issues.apache.org/jira/browse/THRIFT-3753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224992#comment-15224992 ]
James E. King, III commented on THRIFT-3753:
--------------------------------------------
If you interrupt serve() second, a new client might arrive while the first set of clients is being interrupted; will the new client also be interrupted?
> TServerFramework::stop may fail to interrupt connected clients
> --------------------------------------------------------------
>
> Key: THRIFT-3753
> URL: https://issues.apache.org/jira/browse/THRIFT-3753
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Library
> Affects Versions: 0.9.3
> Reporter: Ted Wang
>
> This is a sequence that exposes the race condition:
> (1) Thread-1: in serve(), blocked on accept()
> (2) Thread-2: in stop(), calls interrupt()
> (3) Thread-2: in stop(), in interruptChildren(), checked that socket is valid
> (4) Thread-1: in serve(), unblocked because of interrupt(), calls releaseOneDescriptor
> (5) Thread-2: in interruptChildren(), send fails so clients are not interrupted
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)