[
https://issues.apache.org/jira/browse/THRIFT-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Geyer updated THRIFT-4372:
-------------------------------
Description:
{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 he 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.
was:
{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 he 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 client get stuck while waiting for the remaining bytes.
> 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
>
> {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 he 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)
