[CAMEL-18494] camel-mllp - Allow the ability to set MIN_BUFFER_SIZE for SocketBuffer

• Type: New Feature
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.18.2
• Fix Version/s: 3.18.3, 3.19.0
• Component/s: camel-mllp

Environment

Test environment: current environment is Camel / Quarkus

• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Joseph
• Created: 09/Sep/22 15:42
• Updated: 23/Sep/22 09:34
• Resolved: 15/Sep/22 11:41

Description

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).

Issue Links

• links to: GitHub Pull Request #8421