Integrated: 8343491: javax/management/remote/mandatory/connection/DeadLockTest.java failing with NoSuchObjectException: no such object in table
Kevin Walls
kevinw at openjdk.org
Thu Nov 7 18:16:54 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.
This pull request has now been integrated.
Changeset: 4f5a241e
Author: Kevin Walls <kevinw at openjdk.org>
URL: https://git.openjdk.org/jdk/commit/4f5a241ec11981bcb5f8ab0936b0e821ec5a03ce
Stats: 5 lines in 1 file changed: 4 ins; 0 del; 1 mod
8343491: javax/management/remote/mandatory/connection/DeadLockTest.java failing with NoSuchObjectException: no such object in table
Reviewed-by: lmesnik, sspitsyn, cjplummer
-------------
PR: https://git.openjdk.org/jdk/pull/21884
More information about the serviceability-dev
mailing list