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

Zhihua Deng updated THRIFT-5875:
--------------------------------
    Description: 
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. 

  was:
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. 


> 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)

Reply via email to