[THRIFT-3673] API fails with std::exception after a timeout occured in earlier any API call

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Not A Bug
• Affects Version/s: 0.9.1
• Fix Version/s: 0.10.0
• Component/s: C++ - Library

Environment

Windows

• Flags: Important
• Assignee: Nobuaki Sukegawa
• Reporter: SABU DANIEL
• Created: 25/Feb/16 21:58
• Updated: 03/Apr/16 17:10
• Resolved: 13/Mar/16 00:16

Description

Any API calls( from client to server) fails with std::exception after a timeout occurred in earlier API call.

Steps:
1) Call a Server API which doesn't finish within the socket read timeout
2) This call throws apache::thrift::transport::TTransportException with a TIMEOUT type (Excepted)
3) Call Another API, this fails because the earlier call response data in the socket read buffer.

// Here is the part of generated code in client
void ClientGeneratedClass::recv_[CURRENTAPI_NAME]
{
...
..
..
if (fname.compare([CURRENTAPI_NAME]) != 0)

{ iprot_->skip(::apache::thrift::protocol::T_STRUCT); iprot_->readMessageEnd(); iprot_->getTransport()->readEnd(); }

}
This iprot_->skip doesn't seems to be cleaning the read buffer correctly.

Please advise any workaround or solution for this.

Issue Links

• relates to: THRIFT-3735 JSON protocol left in incorrect state when an exception is thrown during read or write operations