[
https://issues.apache.org/jira/browse/AMQ-6153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher L. Shannon updated AMQ-6153:
----------------------------------------
Fix Version/s: (was: 5.13.1)
5.13.2
5.14.0
> Toggle the TCP transport's ability to size a socket's read and write buffer
> ---------------------------------------------------------------------------
>
> Key: AMQ-6153
> URL: https://issues.apache.org/jira/browse/AMQ-6153
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Transport
> Affects Versions: 5.12.1, 5.13.0
> Environment: Linux
> Reporter: Paul Gale
> Assignee: Christopher L. Shannon
> Priority: Minor
> Fix For: 5.14.0, 5.13.2
>
>
> This improvement only applies when running ActiveMQ on Linux.
> At the moment the TCP transport sets the size of the accepted socket's read
> and write buffer (64k by default). They can be given different sizes using
> the relevant transport connector options.
> However, on Linux once a socket has had either its read or write buffer size
> explicitly set the kernel will not automatically tune its size at run-time.
> Therefore add a new flag to instruct the TCP transport connector to not set
> the size of the socket's buffers. Said flag should default to false for
> backward compatibility.
> If the flag is true the TCP transport will ignore any configured size of the
> socket's buffers. Perhaps print a warning? This will allow the kernel to
> auto-tune the socket's buffer at run-time according to the kernel parameters
> net.ipv4.tcp_rmem and net.ipv4.tcp_wmem.
> Flag name suggestion: disableSocketBufferSizing
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
