[
https://issues.apache.org/jira/browse/THRIFT-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17979331#comment-17979331
]
Zhihua Deng commented on THRIFT-5875:
-------------------------------------
{noformat}
For TProtocolExceptions, the server should send the exception back before
closing the connection.{noformat}
Right, the similar I want to deal with some TTransportExceptions in this jira,
so the user can get the real reason instead of the "Socket is closed by peer".
> ServerContext offers API to catch the thrift exception
> ------------------------------------------------------
>
> Key: THRIFT-5875
> URL: https://issues.apache.org/jira/browse/THRIFT-5875
> Project: Thrift
> Issue Type: Improvement
> Components: Java - Library
> Reporter: Zhihua Deng
> Assignee: Zhihua Deng
> Priority: Major
>
> If we the exception thrown from transport lawyer, such as the
> MESSAGE_SIZE_LIMIT or CORRUPTED_DATA, in order not to pollute the byte
> stream, the server will kill the transport, on the client side it would
> receive the message indicating the socket is killed by peer. It's would be
> nice if we can send the exception back to the client to tell what's happening
> on the server side, the TServerEventHandler deleteContext provides a way for
> such purpose if we can get the exception from the ServerContext.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
