Currently the default value for this parameter covers the default locator and server port values. As a result of this, when launching a locator and then a server on the same system using gfsh, it's possible to see the server fail because the locator has already bound the default server socket. We've actually seen a couple of test runs fail with this issue.
The proposed new range is 41000-61000, which, in addition to not overlapping the other default port values, has the benefit of being a subset of the linux ephemeral ports (for users who care about such things). Please let me know if there are any objections to this change. Here's the current javadoc for this parameter: Description: The allowed range of ports for use in forming an unique membership identifier (UDP), for failure detection purposes (TCP) and to listen on for peer connections (TCP). This range is given as two numbers separated by a minus sign. Minimum 3 values in range are required to successfully startup. Default: 1024-65535
