You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Karl Janke (Jira)" <ji...@apache.org> on 2020/07/06 03:29:00 UTC
[jira] [Updated] (THRIFT-5246) Connection aborted when using buffer
size != 1024
[ https://issues.apache.org/jira/browse/THRIFT-5246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Janke updated THRIFT-5246:
-------------------------------
Patch Info: Patch Available
> Connection aborted when using buffer size != 1024
> -------------------------------------------------
>
> Key: THRIFT-5246
> URL: https://issues.apache.org/jira/browse/THRIFT-5246
> Project: Thrift
> Issue Type: Bug
> Components: netstd - Library
> Affects Versions: 0.13.0
> Reporter: Karl Janke
> Priority: Major
> Attachments: 0001-THRIFT-5246-Don-t-set-_bytesUsed-when-changing-Capac.patch
>
>
> When creating a TBufferedTransport with a size not equal to 1024 the ReadBuffer and WriteBuffer capacity are set.
> The TMemoryBufferTransport.Capacity setter sets _bytesUsed (Length) to the provided value
> When TBufferedTransport.WriteAsync is entered the free space in the buffer is calculated to be 0 and the whole empty buffer is sent on the wire
> This doesn't look to be such an issue in master as TMemoryBufferTransport.Capacity is no longer used to adjust buffer size (constructor used instead). However the bug in Capacity setter still lurks
--
This message was sent by Atlassian Jira
(v8.3.4#803005)