[
https://issues.apache.org/jira/browse/THRIFT-3568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15111637#comment-15111637
]
ASF GitHub Bot commented on THRIFT-3568:
----------------------------------------
Github user andrewcox commented on the pull request:
https://github.com/apache/thrift/pull/807#issuecomment-173754745
One mitigating factor here is our "ThriftServer" class (our most used
server) doesn't use "THeaderTransport" at all, it uses the "THeader" core.
And then some of our servers that *do* use THeaderTransport do it through
TAsyncChannel in a way that it ends up reading a buffer that already contains a
full message, so it would never stall in the middle of a message.
Still though, I believe at least some of our legacy servers still use
THeaderTransport and synchronous I/O, and we've never seen this AFAICT. That's
why I'd like to see the callstack.
> THeader server crashes on readSlow
> ----------------------------------
>
> Key: THRIFT-3568
> URL: https://issues.apache.org/jira/browse/THRIFT-3568
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Library
> Affects Versions: 0.9.4
> Reporter: Aki Sukegawa
> Assignee: Aki Sukegawa
>
> It is essentially caused by readFrame method that is not overriden (but
> hidden).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
