You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Plumet (Jira)" <ji...@apache.org> on 2021/04/23 12:40:00 UTC
[jira] [Updated] (THRIFT-5402) MaxMessageSize reached exception
thrown in TEndpointTransport
[ https://issues.apache.org/jira/browse/THRIFT-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Plumet updated THRIFT-5402:
---------------------------
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.
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.
was:
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.
> 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
> Fix For: 0.14.1
>
>
> 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.3.4#803005)