On Thu, 24 Aug 2023 11:34:13 GMT, Kevin Walls <kev...@openjdk.org> wrote:
> Several tests from test/jdk/sun/tools/jstatd are intermittent. > > Port clashes when run at the same time on the same machine have been a > problem. > The RMI error "no such object in table" can mean a reference on the RMI > server has been GC'd. > Either way, jstatd fails to startup and and the test fails. > > These both have jstatd reporting "Could not bind" which should be recognised > and retried, as we already do for (some) port in use problems. i.e. > JstatdTest.java: the isJstadReady() method (will correct that typo also) > checks for "Port already in use", which can be printed by TCPTransport.java. > > Should update its test to check for "Could not bind". > Should limit the retries also. This pull request has now been integrated. Changeset: 1d025070 Author: Kevin Walls <kev...@openjdk.org> URL: https://git.openjdk.org/jdk/commit/1d0250709a6ee97f5647edff589761bd9d0b7f4c Stats: 11 lines in 1 file changed: 5 ins; 1 del; 5 mod 8314476: TestJstatdPortAndServer.java failed with "java.rmi.NoSuchObjectException: no such object in table" Reviewed-by: msheppar, sspitsyn ------------- PR: https://git.openjdk.org/jdk/pull/15414
