You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "Stu Hood (JIRA)" <ji...@apache.org> on 2010/02/10 04:42:28 UTC

[jira] Updated: (THRIFT-689) Notify client of recoverable protocol errors on java server

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

Stu Hood updated THRIFT-689:
----------------------------

    Attachment: 689.txt

Here is a revised version of Jonathan's patch which ensures that readMessageEnd is called in the exceptional case as well.

> 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, 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.