RFR: 8343491: javax/management/remote/mandatory/connection/DeadLockTest.java failing with NoSuchObjectException: no such object in table

Chris Plummer cjplummer at openjdk.org
Thu Nov 7 16:11:43 UTC 2024


On Mon, 4 Nov 2024 18:15:37 GMT, Kevin Walls <kevinw at openjdk.org> wrote:

> This test is sensitive to timing, and should not run with -Xcomp (like NotifReconnectDeadlockTest.java).
> 
> With -Xcomp, this test can fail on the the conn.getDefaultDomain() call, but if we handle that, it can also fail on the first iteration through the loop, at the call: JMXConnector client = JMXConnectorFactory.connect(addr, env);  
> 
> This test sets a short timeout value for connections, and -Xcomp slows things down greatly.  RMI is gone before the connection is established.

What changed that caused it to suddenly start failing a lot?

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

PR Comment: https://git.openjdk.org/jdk/pull/21884#issuecomment-2462631378


More information about the serviceability-dev mailing list