[
https://issues.apache.org/jira/browse/THRIFT-689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated THRIFT-689:
----------------------------------
Attachment: 689.txt
following the reasoning in THRIFT-378, we add a
TApplicationException.PROTOCOL_ERROR field and use that to relay the protocol
problem, since TApplicationException is the only exception class clients know
how to read from the server.
> 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.
