[THRIFT-3182] TFramedTransport is in an invalid state after frame size exception

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.9.2
• Fix Version/s: 0.10.0
• Component/s: Java - Library
• Patch Info: Patch Available
• Assignee: Marshall Scorcio
• Reporter: Marshall Scorcio
• Created: 09/Jun/15 01:31
• Updated: 26/Jan/19 14:56
• Resolved: 18/Mar/16 18:08

Description

https://github.com/apache/thrift/pull/512

This is necessary because after reading the invalid
frame size from the underlying transport the transport
is left in a bad state. Any following reads will
likely throw more invalid frame size exceptions and
if they don’t they will be reading corrupted messages.

Closing forces the caller to discard the connection and
get a new one.

Issue Links

• is duplicated by: THRIFT-1323 TFramedTransport should throw an exception that distinguishes an oversized frame from a dead client, servers should log that exception