Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Windows
Description
Most TServer stop methods call interrupt on their underlying server transports. TPipeServer::interrupt() doesn't cause acceptImpl to wake up if it is blocked on ConnectNamedPipe. This means the stop method on TServer variants blocks.
Attachments
Issue Links
- is duplicated by
-
THRIFT-1890 C++: Make named pipes server work asynchronously
- Closed