[
https://issues.apache.org/jira/browse/THRIFT-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17761332#comment-17761332
]
Christopher Tubbs commented on THRIFT-5402:
-------------------------------------------
I think this might be related to THRIFT-5371. I think I'm seeing this also in
Java while trying to work around THRIFT-5732
> MaxMessageSize reached exception thrown in TEndpointTransport
> -------------------------------------------------------------
>
> Key: THRIFT-5402
> URL: https://issues.apache.org/jira/browse/THRIFT-5402
> 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.
> Not unimporant side effect, this exception causes the the
> TThreadPoolAsyncServer to stop the connection with the client in question.
> Perhaps this issue is related to THRIFT-5226.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
