[
https://issues.apache.org/jira/browse/THRIFT-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17475257#comment-17475257
]
Plumet commented on THRIFT-5401:
--------------------------------
Hi [~jensg], I finally found the time to create a reproduceable testcase. I've
tested this testcase against the current master. This issue seems to be fixed
when the Thrift server is in the yet unreleased version 0.16 (not in any of the
versions prior to that). It does not seem to matter which Thrift version the
client uses. As far as I'm concerned, this issue can be closed.
I'm looking forward to the next release so I'll be able to use this fix in my
project.
> 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.20.1#820001)
