Skip to content

Conversation

@davidhjp01
Copy link

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 call resetConsumedMessageSize() in TBufferedTransport::readEnd(), which resets remainingMessageSize_. However, our app uses TFramedTransport, which does not include this reset size function. Adding this function fixed the problem.

  • Did you create an Apache Jira ticket? (Request account here, not required for trivial changes)
  • If a ticket exists: Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"?
  • Did you squash your changes to a single commit? (not required, but preferred)
  • Did you do your best to avoid breaking changes? If one was needed, did you label the Jira ticket with "Breaking-Change"?
  • If your change does not involve any code, include [skip ci] anywhere in the commit message to free up build resources.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant