David Lieberman commented on THRIFT-2954:

Following on my previous comment:
This happens with TBinaryProtocol only; if I switch to TJSONProtocol I get 
exceptions, e.g.:
thrift.protocol.TProtocol.TProtocolException: Bad data encounted in numeric data
thrift.protocol.TProtocol.TProtocolException: Unexpected character: B

I'll try and find some time to review how the JSON protocol casts the values 
and see if I can do the same thing for the Binary protocol. 

> calling function with parameter type different as defined in idl breaks the 
> connection
> --------------------------------------------------------------------------------------
>                 Key: THRIFT-2954
>                 URL: https://issues.apache.org/jira/browse/THRIFT-2954
>             Project: Thrift
>          Issue Type: Bug
>          Components: Python - Compiler, Python - Library
>    Affects Versions: 0.9.2
>         Environment: tried with python server/client and also with c++ server 
> with python client
>            Reporter: Nitin Kumar
>            Priority: Critical
> say my idl (.thrift) file defines a function
> void fn(1: string if_name);
> if I call this function as fn(3) the connection get closed, hence not 
> allowing next set of function to be called. (function call has been kept 
> within exception handling)
> but for other cases like if we call this function with 2 params in place of 1 
> as expected by function. it just thrown exception but does not close the 
> connection.

This message was sent by Atlassian JIRA

Reply via email to