Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-6153

Toggle the TCP transport's ability to size a socket's read and write buffer

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.12.1, 5.13.0
    • Fix Version/s: 5.13.2, 5.14.0
    • Component/s: Transport
    • Labels:
      None
    • Environment:

      Linux

      Description

      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

        Attachments

          Activity

            People

            • Assignee:
              cshannon Christopher L. Shannon
              Reporter:
              paulgale Paul Gale
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: