Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Windows
Description
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.