Hi devs,
We have noticed that some peer-to-peer connections use ports outside the
range defined by the membership-port-range (41000-61000) parameter:
[vm1] membership-port-range=41000-61000
[vm1] [debug 2022/05/02 11:15:57.968 CEST server-1 Connection(1)-192.168.1.36> tid=0x1a] starting pee
Just a quick reminder that all distributedTests should go in
src/distributedTest.
A test should only be considered an acceptanceTest if it uses GfshRule to
launch the locator and server processes, and it should only use User APIs
for everything (configuration, initiating operations and validating
I think the membership-port-range determines the port that the server side of
the TCP socket is listening on.
What I see in your log statement is the port number of the client side of the
socket (where it says localport=37392). The port for the client side of a
socket comes from the ephemeral p
