RFR: 8314476: TestJstatdPortAndServer.java failed with "java.rmi.NoSuchObjectException: no such object in table"

[Kevin Walls]

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.

-------------

Commit messages:
 - 8314476: TestJstatdPortAndServer.java failed with "java.rmi.NoSuchObjectException: no such object in table"

Changes: https://git.openjdk.org/jdk/pull/15414/files
 Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=15414&range=00
  Issue: https://bugs.openjdk.org/browse/JDK-8314476
  Stats: 9 lines in 1 file changed: 3 ins; 1 del; 5 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