You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "Jens Geyer (JIRA)" <ji...@apache.org> on 2015/07/07 22:31:04 UTC

[jira] [Comment Edited] (THRIFT-3225) Fix TPipeServer unpredictable behavior on close

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

Jens Geyer edited comment on THRIFT-3225 at 7/7/15 8:30 PM:
------------------------------------------------------------

True. But that implies that the whole design is broken. Feel free to reopen, I saw your reply too late. Sorry.


was (Author: jensg):
True. But that implies that the whole design is broken.

> Fix TPipeServer unpredictable behavior on close
> -----------------------------------------------
>
>                 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
>
>
> If TPipeServer::close() is invoked from other thread than the thread that is blocked on TPipeServer::serve() the handle may be closed by each thread while should be closed only once.
> I propose to solve the issue by synchronizing access to close() method.



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