You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Pascal Qu (JIRA)" <ji...@apache.org> on 2011/03/01 07:31:37 UTC
[jira] Updated: (THRIFT-1076) Erlang Thrift socket server has a bug
that causes java thrift client of framed binary client to throw "out of
sequence" exception
[ https://issues.apache.org/jira/browse/THRIFT-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pascal Qu updated THRIFT-1076:
------------------------------
Attachment: thrift_protocol.erl
you can search the word "seq" to find my change. If any issue, please feel free to contact me.
> 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
> Priority: Critical
> Fix For: 0.5
>
> Attachments: thrift_protocol.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