Uploaded image for project: 'Red Hat Build of Apache Camel for Quarkus'
  1. Red Hat Build of Apache Camel for Quarkus
  2. CEQ-4846

back port of CAMEL-18494 - camel-mllp - Allow the ability to set MIN_BUFFER_SIZE for SocketBuffer

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • camel-quarkus-2.7-GA
    • Camel Quarkus, Camel-3
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • 0

      See https://issues.apache.org/jira/browse/CAMEL-18494

       
      When payloads are known to be always larger that the hardcoded MIN_BUFFER_SIZE of 2048, this results in the resizing of the buffer.

      https://github.com/apache/camel/blob/c4b5791237bbf27af7b54bbd0d14b7c6944dff1f/components/camel-mllp/src/main/java/org/apache/camel/component/mllp/internal/MllpSocketBuffer.java#L39

      There is also the belief that when a gc event occurs, the buffer then returns to the default size of MIN_BUFFER_SIZE, which again results in another resizing of the buffer when larger than MIN_BUFFER_SIZE payloads arrive.

      It is the hope that allowing for a customized MIN_BUFFER_SIZE would result in an overall faster sustained throughput when the payload size is known to be larger than MIN_BUFFER_SIZE (2048).

          1.
          Documentation Sub-task Closed Major Unassigned
          2.
          Productization Sub-task Closed Major Unassigned
          3.
          Review Test Sub-task Closed Major Unassigned
          4.
          Development Sub-task Closed Major Unassigned

              Unassigned Unassigned
              rdorobek@redhat.com Russell Dorobek
              Archiver:
              fmongiar@redhat.com Francesco Mongiardo

                Created:
                Updated:
                Resolved:
                Archived: