[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    Re: RFR: 8314476: TestJstatdPortAndServer.java failed with "java.rmi.NoSuchObjectException: no such 
From:       Kevin Walls <kevinw () openjdk ! org>
Date:       2023-08-29 8:54:13
Message-ID: _gx66iZySxUwGTI88t_7MiyXmQ15V6Fs3kNpyO6WBZU=.6da98252-d206-4f11-a1c8-b1d406d3c425 () github ! com
[Download RAW message or body]

On Thu, 24 Aug 2023 21:38:41 GMT, Kevin Walls <kevinw@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.
> 
> Kevin Walls has updated the pull request incrementally with one additional commit \
> since the last revision: 
> Modernisation

Thanks Mark and Seguei!

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

PR Comment: https://git.openjdk.org/jdk/pull/15414#issuecomment-1697030288


[prev in list] [next in list] [prev in thread] [next in thread]