You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "Jens Geyer (Jira)" <ji...@apache.org> on 2025/06/04 21:46:00 UTC

[jira] [Updated] (THRIFT-5874) Introduce new type MESSAGE_SIZE_LIMIT in TTransportException

     [ https://issues.apache.org/jira/browse/THRIFT-5874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jens Geyer updated THRIFT-5874:
-------------------------------
    Component/s: Delphi - Library
                     (was: Java - Library)

> Introduce new type MESSAGE_SIZE_LIMIT in TTransportException
> ------------------------------------------------------------
>
>                 Key: THRIFT-5874
>                 URL: https://issues.apache.org/jira/browse/THRIFT-5874
>             Project: Thrift
>          Issue Type: Improvement
>          Components: Delphi - Library
>            Reporter: Jens Geyer
>            Assignee: Jens Geyer
>            Priority: Major
>             Fix For: 0.22.0
>
>
> If the transport reads more bytes than the configured max message size, it will throw the 
> the TTransportException with the type TTransportException.END_OF_FILE. This could be a problem when the TThreadPoolServer ignore the exception and kill the connection silently, the client will receive the 'Socket closed by peer' exception, but there is no message in server to tell what's happening.
> In my idea, rather than throwing the exception with END_OF_FILE, we should flag this exception with a new type SIZE_LIMIT.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)