Uploaded image for project: 'Thrift'
  1. Thrift
  2. THRIFT-5402

MaxMessageSize reached exception thrown in TEndpointTransport

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • netstd - Library
    • None

    • Windows

    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.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. THRIFT-5371 Max Message Size is eventually exceeded when using TFramedTransport

          • Major - Major loss of function.
          • Open

          Activity

            People

              Unassigned Unassigned
              Plumet Plumet
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: