You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/10/25 20:38:00 UTC
[jira] [Commented] (THRIFT-4372) Pipe write operations across a
network are limited to 65,535 bytes per write.
[ https://issues.apache.org/jira/browse/THRIFT-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219478#comment-16219478 ]
ASF GitHub Bot commented on THRIFT-4372:
----------------------------------------
GitHub user Jens-G opened a pull request:
https://github.com/apache/thrift/pull/1402
THRIFT-4372 Pipe write operations across a network are limited to 65,…
…535 bytes per write
Client: C#
Patch: Jens Geyer
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Jens-G/thrift THRIFT-4372
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/thrift/pull/1402.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1402
----
commit ccfc002a480c9ed23b50674c3fd76a280750bbb0
Author: Jens Geyer <je...@apache.org>
Date: 2017-10-25T20:30:23Z
THRIFT-4372 Pipe write operations across a network are limited to 65,535 bytes per write
Client: C#
Patch: Jens Geyer
----
> 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
> 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 server acts as if he had written all the bytes (in fact, he did)
> * but the remainder of ~ 65535 bytes is just lost somewhere and never reaches the client
> Consequently, the client get stuck while waiting for the remaining bytes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)