Reset consumed message size in TFramedTransport::readEnd() #3228
+2
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following the issue reported in THRIFT-5492 and further discussed here, we are encountering a similar problem in our application. After many message exchanges, we receive an error stating
no more data to read. In #2496, the issue was resolved by adding a callresetConsumedMessageSize()inTBufferedTransport::readEnd(), which resetsremainingMessageSize_. However, our app usesTFramedTransport, which does not include this reset size function. Adding this function fixed the problem.[skip ci]anywhere in the commit message to free up build resources.