Zhihua Deng created THRIFT-5858:
-----------------------------------
Summary: Introduce a new type SIZE_LIMIT in TTransportException
Key: THRIFT-5858
URL: https://issues.apache.org/jira/browse/THRIFT-5858
Project: Thrift
Issue Type: Bug
Reporter: Zhihua Deng
If the transport reads more bytes than the configured max message size, it will
throw the
the TTransportException with the type TTransportException.END_OF_FILE. This
could be a problem when the TThreadPoolServer ignore the exception and kill the
connection silently, the client will receive the 'Socket closed by peer'
message, but there is no message in server to tell what's happening.
In my idea, rather than throwing the exception with END_OF_FILE, we should flag
this exception with a new type SIZE_LIMIT.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
