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

Sebastian Zenker updated THRIFT-3496:
-------------------------------------
    Description: 
I extended the C++ unit tests to send a second request using the same generated 
client instance (without recreating it). This causes the following two problems:

1.) the client still has the first request in it's output buffer causing it to 
send the first request again and again

2.) the wrong cob gets called, as sending the second request will always 
overwrite the cob of the first request

  was:
I extended the C++ unit tests to send a second request using the same generate 
client instance (without recreating it). This causes the following two problems:

1.) the client still has the first request in it's output buffer causing it to 
send the first request again and again

2.) the wrong cob gets called, as sending the second request will always 
overwrite the cob of the first request


> C++: Cob style client fails when sending a consecutive request
> --------------------------------------------------------------
>
>                 Key: THRIFT-3496
>                 URL: https://issues.apache.org/jira/browse/THRIFT-3496
>             Project: Thrift
>          Issue Type: Bug
>          Components: C++ - Compiler, C++ - Library
>    Affects Versions: 1.0
>         Environment: Linux
>            Reporter: Sebastian Zenker
>            Priority: Critical
>              Labels: easyfix
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> I extended the C++ unit tests to send a second request using the same 
> generated client instance (without recreating it). This causes the following 
> two problems:
> 1.) the client still has the first request in it's output buffer causing it 
> to send the first request again and again
> 2.) the wrong cob gets called, as sending the second request will always 
> overwrite the cob of the first request



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to