[jira] [Commented] (THRIFT-3238) Fix TNamedPipeServer can be interrupted by faulty client

["James E. King, III (JIRA)" <ji...@apache.org>]

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

James E. King, III commented on THRIFT-3238:
--------------------------------------------

Does the priority of critical still make sense for this particular defect with respect to other defects labeled as such?
Would it be possible to submit a pull request in github for the fix?

> Fix TNamedPipeServer can be interrupted by faulty client
> --------------------------------------------------------
>
>                 Key: THRIFT-3238
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3238
>             Project: Thrift
>          Issue Type: Bug
>          Components: C++ - Library
>    Affects Versions: 0.9.2
>         Environment: Windows
>            Reporter: Paweł Janicki
>            Priority: Critical
>         Attachments: 0001-Fix-TNamedPipeServer-can-be-interrupted-by-faulty-cl.patch, 0002-THRIFT-3238.-cpp-Fix-TNamedPipeServer-can-be-interru.patch
>
>
> A faulty or hostile client can cause TNamedPipeServer to be interrupted and return from serve(). The client that causes such effect just needs to open and immediately close TPipe transport.
> Caused by not handling some NamedPipe error codes.



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