> Port clashes happening when several tests from test/jdk/sun/tools/jstatd run > at the same time on the same machine. > > There is logic in here for detecting this, but it's not working. > > We recently saw this fail with a port in use, and the failure is: > > [Jstatd-Thread] Could not bind //:33859/TestJstatdServer to RMI Registry > [Jstatd-Thread] java.rmi.NoSuchObjectException: no such object in table > > In JstatdTest.java, the isJstadReady() method (will correct that typo also) > checks for "Port already in use", which can be printed by TCPTransport.java. > But that is not what we see in this failure. > Should update its test to check for "Could not bind". > Should limit the retries also.
Kevin Walls has updated the pull request incrementally with one additional commit since the last revision: Less specific error message, could be ports or other failure.. ------------- Changes: - all: https://git.openjdk.org/jdk/pull/15414/files - new: https://git.openjdk.org/jdk/pull/15414/files/f5bdf903..67fd896d Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=15414&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=15414&range=00-01 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/15414.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/15414/head:pull/15414 PR: https://git.openjdk.org/jdk/pull/15414
