[ https://issues.apache.org/jira/browse/THRIFT-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12910395#action_12910395 ]
Ryan King commented on THRIFT-639: ---------------------------------- What transport are you using? > Timeouts Interrupting Read Can Leave Data in Read Queue, Corrupting Later > Reads > ------------------------------------------------------------------------------- > > Key: THRIFT-639 > URL: https://issues.apache.org/jira/browse/THRIFT-639 > Project: Thrift > Issue Type: Bug > Components: Ruby - Library > Affects Versions: 0.1, 0.2 > Reporter: Emily Leathers > Priority: Minor > > When a Timeout interrupts a client that is reading a Thrift response, the > client may leave unread bytes in the read queue. If this transport > instance/queue is reused in a later request, the extra bytes will corrupt > that later response. > We're currently working around this by having the rescue blocks of our > TimeoutExceptions close the transport so that subsequent requests will have > to create a new, clean one. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.