Hi, thanks for doing that. You could have done a force push on your original PR... As you can see the build status isn't getting to green (like ever)... so I have some work to do to fix this up.
- Jim On Tue, Feb 27, 2018 at 5:05 PM, Buğra Gedik (JIRA) <j...@apache.org> wrote: > > [ https://issues.apache.org/jira/browse/THRIFT-4465?page= > com.atlassian.jira.plugin.system.issuetabpanels:comment- > tabpanel&focusedCommentId=16379366#comment-16379366 ] > > Buğra Gedik commented on THRIFT-4465: > ------------------------------------- > > [~jking3]: would it be possible to get this in: Here is the squashed > version: https://github.com/apache/thrift/pull/1497 > > > 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) >
