[jira] [Commented] (THRIFT-4372) Pipe write operations across a network are limited to 65,535 bytes per write.

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

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

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

I added csharp as a multiplexed client for cross testing in some work I am doing and the "huge" send interacts with the rs server badly.  I'll disable the tests for now; it seems to be the rs server, since the csharp client appears to be okay against other languages.

> Pipe write operations across a network are limited to 65,535 bytes per write. 
> ------------------------------------------------------------------------------
>
>                 Key: THRIFT-4372
>                 URL: https://issues.apache.org/jira/browse/THRIFT-4372
>             Project: Thrift
>          Issue Type: Bug
>          Components: C# - Library, Delphi - Library
>            Reporter: Jens Geyer
>            Assignee: Jens Geyer
>            Priority: Critical
>             Fix For: 0.11.0
>
>
> {quote}Pipe write operations across a network are limited to 65,535 bytes per write. For more information regarding pipes, see the Remarks section.{quote}
> Source: [WriteFileEx function|https://msdn.microsoft.com/en-us/library/windows/desktop/aa365748(v=vs.85).aspx]
> I managed to run into exactly that limit today. Patch follows.
> Symptom is that
>  * the writing end  acts as if it had written all the bytes (in fact, it did)
>  * but the remainder of ~ 65535 bytes is just lost somewhere and never reaches the reading end
> Consequently, the process at the reading end of the pipe gets stuck while waiting for the remaining bytes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)