Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
The DRPC tests should avoid using Utils.getAvailablePort. That method for getting an unused port is prone to race conditions, since there is no guarantee that a port that is found using getAvailablePort is still available when the returned port is actually used to create a socket. There is also no guarantee that the same port is not returned to multiple threads.
The tests should instead pass a random port to the servers underlying DRPCServer, and ask those servers which ports they're running on when they've started.
Attachments
Issue Links
- links to