[
https://issues.apache.org/jira/browse/THRIFT-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jens Geyer resolved THRIFT-5401.
--------------------------------
Fix Version/s: 0.16.0
Resolution: Fixed
> MaxMessageSize reached exception thrown in TEndpointTransport
> -------------------------------------------------------------
>
> Key: THRIFT-5401
> URL: https://issues.apache.org/jira/browse/THRIFT-5401
> Project: Thrift
> Issue Type: Bug
> Components: netstd - Library
> Environment: Windows
> Reporter: Plumet
> Priority: Major
> Fix For: 0.16.0
>
>
> When using the TThreadPoolAsyncServer with sockettransport, framedtransport
> and binaryprotocol a "MaxMessageSize reached" is thrown when a client first
> sends a smaller message of type void and then sends a bigger message of type
> void.
> The problem is that the KnownMessageSize is not reset when a new message gets
> sent in TEndpointTransport.
> Perhaps this issue is related to THRIFT-5226.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
