Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
TcpIpConnectionManager puts connections in map under remote endpoint bind address, not under the address to which we are connecting #11256
The behaviour was observed when testing WAN replication with the discovery SPI on EC2. The WAN connection manager will try and connect to the target endpoint by calling
The solution might be disabling the spoofing checks by using
This works mainly fine, the only remaining problem is that the
This will actually be the private IP of the remote endpoint so even though the connection was requested on the public IP :
And because of this, the WAN connection manager will retry reestablishing a connection which already exists, just under a different address.