[
https://issues.apache.org/jira/browse/THRIFT-760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859797#action_12859797
]
Marc de Palol commented on THRIFT-760:
--------------------------------------
Indeed.
This bug caused me serious trouble. Under high load the server can respond a
message to a wrong client. Then the client thinks that the response is right
and continues its workflow with wrong data, instead it should fail and retry
the call. Of course this should be handled at application level, but at least
there should be a way to know that the data it got is not what's meant to be.
> Generated client code does not set or check the sequence ID in messages
> -----------------------------------------------------------------------
>
> Key: THRIFT-760
> URL: https://issues.apache.org/jira/browse/THRIFT-760
> Project: Thrift
> Issue Type: Bug
> Components: Compiler (Java)
> Affects Versions: 0.2
> Reporter: James Grant
> Priority: Minor
> Attachments: thrift-seqid.patch
>
>
> The sequence ID is never set in the generated client code. It is also never
> checked. This means that if you continue to use a connection after a socket
> timeout the returned results can arrive out of sequence. When this happens an
> exception should be thrown so that incorrect results are never returned.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
