Fix for Multipart Message Issue on some Windows Servers
"During edge testing we ran into the bug PLATFORM-1841. When a connection was lightly loaded and had little or no activity, a multipart message sent from the server to the edge would fail to send the last chunk until it received a message of any sort from the edge. The end result would be a message timeout on the server. Quite often the timeout would be avoided because of the fact that the edge regularly sends pings to the server, but since the default ping rate is longer than the default message timeout you would often see multipart messages from the server to the edge timing out.
We were able to resolve this issue by modifying the SO_SNDBUF value that Tomcat uses for sockets. This controls the size of the output buffer used by TCP. Setting it to something larger than our message chunk size of 8192 prevented the timeouts and ensured that all the chunks were delivered as expected.
This config option can be set in the Tomcat Connector configuration in your server.xml. Here is an example. Note the socket.txBufSize option at the bottom:
<Connector port="443"
|
"
