[jira] Closed: (THRIFT-1076) Erlang Thrift socket server has a bug that causes java thrift client of framed binary client to throw "out of sequence" exception

["Bryan Duxbury (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/THRIFT-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Duxbury closed THRIFT-1076.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.5)
                   0.7
         Assignee: Pascal Qu

I just committed this patch to TRUNK. Thanks for the patch, Pascal!

I noticed that you had it listed as "fix for" 0.5, but 0.5 is already shipped. Generally, I'd rather not go down the road of maintenance releases for older versions, but if you *really* want to do that, start a thread on the mailing list.

> Erlang Thrift socket server has a bug that causes java thrift client of framed binary client to throw "out of sequence" exception
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-1076
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1076
>             Project: Thrift
>          Issue Type: Bug
>          Components: Erlang - Library
>    Affects Versions: 0.5
>         Environment: CentOS5.5, Erlang 13B04, thrift 0.5
>            Reporter: Pascal Qu
>            Assignee: Pascal Qu
>            Priority: Critical
>             Fix For: 0.7
>
>         Attachments: seq.diff, thrift_processor.erl
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Repro step:
> 1) I defined a thrift file like below:
> namespace java com.foo.jabber
> service FrontendService {
>   bool isUserOnline(1:string userId, 2:string userDomain)
> }
> 2) I implemented an erlang thrift server of framed, binary;
> 3) I use a java thrift framed+binary client to talk to the server;
> 4) I always got an exception of "out of sequence" while call isUserOnline(), while the thrift server had responsed to the request.
> After some investigation, i found the field seq of reply's protocol_message_begin is hardcoded as 0 in thrift_processor.erl. I think it should be the save as that of request. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira