You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Paweł Janicki (JIRA)" <ji...@apache.org> on 2015/07/09 09:15:04 UTC

[jira] [Commented] (THRIFT-3225) Fix TPipeServer unpredictable behavior on interrupt()

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

Paweł Janicki commented on THRIFT-3225:
---------------------------------------

I rebased to latest master.
The patch 0001 is to be abadoned then.

Changed description. (for future: Should I open new issue and abadon this or update this issue, if changed the issue description?)

There is similiar problem with interrupt() then.
The handle may be closed by interrupting thread while still used by servicing thread.



> Fix TPipeServer unpredictable behavior on interrupt()
> -----------------------------------------------------
>
>                 Key: THRIFT-3225
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3225
>             Project: Thrift
>          Issue Type: Bug
>          Components: C++ - Library
>    Affects Versions: 0.9.2
>         Environment: Windows
>            Reporter: Paweł Janicki
>            Assignee: Paweł Janicki
>            Priority: Critical
>              Labels: patch
>             Fix For: 0.9.3
>
>         Attachments: 0001-THRIFT-3225.-cpp-Fix-TPipeServer-unpredictable-behav.patch, 0002-THRIFT-3225.-cpp-Fix-TPipeServer-unpredictable-behav.patch
>
>
> If TPipeServer::interrupt() is invoked from other thread than the thread that is blocked on TPipeServer::serve() the handle may be closed by interrupting thread while still used by servicing thread.



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