[
https://issues.apache.org/jira/browse/THRIFT-2954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15583935#comment-15583935
]
David Lieberman commented on THRIFT-2954:
-----------------------------------------
I can reproduce this in my production environment as well as vagrant instance.
We have an IDL with a defined type as double, but accept int or float types as
input and this reliably causes the issue described.
> 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
(v6.3.4#6332)
