[
https://issues.apache.org/jira/browse/THRIFT-4465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333601#comment-16333601
]
Buğra Gedik commented on THRIFT-4465:
-------------------------------------
OK, I'm creating a PR now. I saw 2 other places where this exact same line was
already commented out. I thought a better fix is to kill these commented out
lines altogether, so that they do not confuse the developers going forward.
> TNonblockingServer throwing THRIFT LOGGER: TConnection::workSocket():
> THRIFT_EAGAIN (unavailable resources)
> -----------------------------------------------------------------------------------------------------------
>
> Key: THRIFT-4465
> URL: https://issues.apache.org/jira/browse/THRIFT-4465
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Library
> Affects Versions: 0.11.0
> Reporter: Buğra Gedik
> Priority: Critical
>
> Once I upgraded to 0.11.0, I'm getting the following error occasionally:
> THRIFT LOGGER: TConnection::workSocket(): THRIFT_EAGAIN (unavailable
> resources)
> I tracked this to the following change:
> [https://github.com/apache/thrift/commit/808d143245f4f5c30600fab31cf9db854cbf5b48#diff-fe8fec8ec38ea35df64cfcc305e3ab08]
>
> {code:java}
> // Work the socket right away
> - // workSocket();
> + workSocket();
> {code}
> While adding SSL support, @dthaluru has re-activated the above line. From my
> own testing, this causes occasional THRIFT_EAGAIN exceptions. It seems like
> this is due to calling workSocket() too early and the socket gets a read call
> in non-blocking mode before it has data.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
