[
https://issues.apache.org/jira/browse/THRIFT-3225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14617380#comment-14617380
]
Hudson commented on THRIFT-3225:
--------------------------------
SUCCESS: Integrated in Thrift #1594 (See
[https://builds.apache.org/job/Thrift/1594/])
THRIFT-3225 Fix TPipeServer unpredictable behavior on close (jensg: rev
f48588f124fb8636f94bf23d098d4483f077e2de)
* lib/cpp/src/thrift/transport/TPipeServer.cpp
Revert "THRIFT-3225 Fix TPipeServer unpredictable behavior on close" (jensg:
rev 17044564494a4e6354a49670c281555f9704ecc1)
* lib/cpp/src/thrift/transport/TPipeServer.cpp
> 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)
