When running a test that concurrently binds to a TCP port range, I found that there is a concurrency issue: The JDK socket implementation might have successfully bound but only failed on listening. 

Tested with JDK 21. 

PR with a failing test case: https://github.com/ahus1/JGroups/pull/new/is-JGRP-2912-concurrent-binding-to-tcp-fails    

Possibly remedy: Always create new sockets if the binding fails, and do not reuse the socket to bind to another port in the range.