JDK-8308366 : javax/management/remote/mandatory/loading/RMIDownloadTest.java timed out
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 21
  • Priority: P4
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: windows
  • CPU: x86_64
  • Submitted: 2023-05-18
  • Updated: 2025-10-15
  • Resolved: 2025-10-15
Related Reports
Relates :  
Relates :  
Sub Tasks
JDK-8308472 :  
JDK-8369894 :  
Description
The following test timed out in the JDK21 CI:

javax/management/remote/mandatory/loading/RMIDownloadTest.java

Here's a snippet from the log file:

#section:main
----------messages:(9/468)----------
command: main -Djava.security.manager=allow RMIDownloadTest send without
reason: User specified action: run main/othervm -Djava.security.manager=allow RMIDownloadTest send without 
started: Thu May 18 08:39:45 UTC 2023
Mode: othervm [/othervm specified]
Additional options from @modules: --add-modules java.management,java.management.rmi
Timeout information:
--- Timeout information end.
finished: Thu May 18 08:51:06 UTC 2023
elapsed time (seconds): 680.897
----------configuration:(3/66)----------
Boot Layer
  add modules: java.management java.management.rmi

----------System.out:(4/138)----------
Testing we can send an object from client to server
Testing without codebase, should fail
Sending object...
Timeout refired 480 times
----------System.err:(6/611)----------
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by RMIDownloadTest (file:/C:/sb/prod/1684398797/testoutput/test-support/jtreg_open_test_jdk_jdk_jmx/classes/4/javax/management/remote/mandatory/loading/RMIDownloadTest.d/)
WARNING: Please consider reporting this to the maintainers of RMIDownloadTest
WARNING: System::setSecurityManager will be removed in a future release
May 18, 2023 8:39:48 AM javax.management.remote.rmi.RMIConnectionImpl unwrap
WARNING: Failed to unmarshall object: java.lang.ClassNotFoundException: Zooby
----------rerun:(49/5972)*----------

<snip>

result: Error. Program `c:\ade\mesos\work_dir\jib-master\install\jdk-21+23-1993\windows-x64-debug.jdk\jdk-21\fastdebug\bin\java' timed out (timeout set to 480000ms, elapsed time including timeout handling was 680881ms).

Comments
Like 8308352 and 8309069 (ConnectionTest and DeadLockTest), this is a timeout, on Windows only, when the test tries (in a Virtual thread) to connect, and it parks forever. (although here it's not an intentionally closed connection). WEPoller thread is still idle. This one IS an "othervm" test. So this also may be the Windows issue described in 8282726.
07-06-2023

There are several tests with possibly the same issue, not previously known to work in a Virtual thread started by jtreg. Here, the test running in a Virtual thread calls setAttribute on an MBeanServerConnection, and blocks in the connect. But I can't make these tests fail running them on their own or in a tier5 of tests.
25-05-2023