[
https://issues.apache.org/jira/browse/THRIFT-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829148#action_12829148
]
Todd Lipcon commented on THRIFT-689:
------------------------------------
Just looked over the patch at Jonathan's request.
Here's the issue I see - if it fails to read args, it's likely that the
connection is then "out of sync", right? How are we sure that connection is a
quiescent state after the failed read, such that we can read a new RPC?
> Notify client of recoverable protocol errors on java server
> -----------------------------------------------------------
>
> Key: THRIFT-689
> URL: https://issues.apache.org/jira/browse/THRIFT-689
> Project: Thrift
> Issue Type: Improvement
> Components: Compiler (Java)
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Attachments: 689.txt
>
>
> As described in CASSANDRA-711, the java thrift server disconnects clients
> that send an invalid message (such as a method call with null arguments to
> required parameters). We should send an exception back to the client instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
