[ https://issues.redhat.com/browse/JGRP-2504?page=com.atlassian.jira.plugin... ] Bela Ban edited comment on JGRP-2504 at 9/30/20 9:50 AM: --------------------------------------------------------- I made the following changes: * For TCP, I set the receive buffer size on {{ServerSocket}} _before_ calling {{bind()}}. This should be copied to the sockets received by {{accept()}}. However, I read that this behavior is implementation-dependent * Ditto for TCP_NIO2 and {{ServerSocketChannel}} * For {{DatagramSocket}} and {{MulticastSocket}}, there is no need to do this, as receive- and send buffer sizes can be set after calling {{bind()}}. Unfortunately, I cannot reproduce this, as I don't have 2 boxes in different geos. Please verify this fix works for you and re-open if needed. I was also under the impression that setting buffer sizes on TCP sockets is only an indication and the OS can choose to ignore this. As TCP adapts the receive-window size dynamically, I'm also a bit surprised that this didn't happen in your case? Perhaps the receive buffer size is the *max size* of the TCP receive window...? was (Author: belaban): I made the following changes: * For TCP, I set the receive buffer size on {{ServerSocket}} _before_ calling {{bind()}}. This should be copied to the sockets received by {{accept()}}. However, I read that this behavior is implementation-dependent * Ditto for TCP_NIO2 and {{ServerSocketChannel}} * {{For {{DatagramSocket}}}} and {{MulticastSocket}}, there is no need to do this, as receive- and send buffer sizes can be set after calling {{bind()}}. Unfortunately, I cannot reproduce this, as I don't have 2 boxes in different geos. Please verify this fix works for you and re-open if needed. I was also under the impression that setting buffer sizes on TCP sockets is only an indication and the OS can choose to ignore this. As TCP adapts the receive-window size dynamically, I'm also a bit surprised that this didn't happen in your case? Perhaps the receive buffer size is the *max size* of the TCP receive window...? -- This message was sent by Atlassian Jira (v7.13.8#713008)