[
https://issues.apache.org/jira/browse/THRIFT-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392509#comment-17392509
]
Jens Geyer edited comment on THRIFT-5401 at 8/3/21, 8:08 PM:
-------------------------------------------------------------
May I ask for a reproducible *testcase* and/or to test it again against
*current* *master*? That's simply not enough info to act upon.
was (Author: jensg):
May I ask for a reproducible testcase and/or to test it again against
{color:#505f79}current{color} master? That's simply not enough info to act upon.
> 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
>
> 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.3.4#803005)
