[
https://issues.apache.org/jira/browse/THRIFT-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pascal Bach updated THRIFT-3704:
--------------------------------
Attachment: 0001-Treat-the-case-where-we-are-not-able-to-refill-the-b.patch
I came up with the solution to treat the case where the buffer could not be
refilled the same as when there is an EOF reached.
I'm not sure it is correct to do this but I couldn't find anything that's not
working. Maybe somebody with a deeper understanding can give some feedback.
> "TConnectedClient died: Could not refill buffer" message shown when using
> HTTP Server
> -------------------------------------------------------------------------------------
>
> Key: THRIFT-3704
> URL: https://issues.apache.org/jira/browse/THRIFT-3704
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Library
> Affects Versions: 0.9.3
> Environment: Linux 64bit and Linux arm
> Reporter: Pascal Bach
> Attachments:
> 0001-Modify-tutorial-server-to-use-HTTP-and-JSON-to-repro.patch,
> 0001-Treat-the-case-where-we-are-not-able-to-refill-the-b.patch
>
>
> When using {{THttpTransport}} after every request the server prints the
> following message:
> {{TConnectedClient died: Could not refill buffer}}
> However the operation seems to be completed successfully.
> It doesn't matter what protocol is used (JSON, Binary). The issue can be
> observed independent of the client used (C++, JavaScript in Browser).
> The error is thrown in the {{THttpTransport::refill}} function in the case
> where read from the transport returns 0.
> I'm not sure if throwing an exception there is really necessary?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
