JDK-8360157 : Multiplex protocol not removed from RMI specification Index
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.rmi
  • Affected Version: 25,26
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2025-06-20
  • Updated: 2025-06-23
  • Resolved: 2025-06-23
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 25 JDK 26
25Fixed 26 masterFixed
Related Reports
Causes :  
Description
The following test failed in the JDK26 CI:

jdk/javadoc/doccheck/checks/jdkCheckLinks.java

Here's a snippet from the log file:

#section:main
----------messages:(7/292)----------
command: main -Ddoccheck.checks=links DocCheck
reason: User specified action: run main/othervm -Ddoccheck.checks=links DocCheck 
started: Fri Jun 20 21:39:13 UTC 2025
Mode: othervm [/othervm specified]
Process id: 1883113
finished: Fri Jun 20 21:39:25 UTC 2025
elapsed time (seconds): 12.036
----------configuration:(0/0)----------
----------System.out:(0/0)----------
----------System.err:(35/1930)----------
test: test
docs/specs/rmi/index.html:178: id not found: docs/specs/rmi/protocol.html#rmis-multiplexing-protocol

Link Checker Report
Checked 10857 files.
Found 1266338 references to 100404 anchors in 10857 files and 153 other URIs.
     1 missing ids
Exception running test test: java.lang.Exception: One or more HTML checkers failed: [java.lang.RuntimeException: LinkChecker encountered errors; see log above.]
java.lang.Exception: One or more HTML checkers failed: [java.lang.RuntimeException: LinkChecker encountered errors; see log above.]
	at DocCheck.runCheckersSequentially(DocCheck.java:194)
	at DocCheck.test(DocCheck.java:179)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:565)
	at toolbox.TestRunner.runTests(TestRunner.java:91)
	at toolbox.TestRunner.runTests(TestRunner.java:73)
	at DocCheck.main(DocCheck.java:98)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:565)
	at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
	at java.base/java.lang.Thread.run(Thread.java:1474)

1 errors
java.lang.Exception: 1 errors found
	at toolbox.TestRunner.runTests(TestRunner.java:119)
	at toolbox.TestRunner.runTests(TestRunner.java:73)
	at DocCheck.main(DocCheck.java:98)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:565)
	at com.sun.javatest.regtest.agent.MainWrapper$MainTask.run(MainWrapper.java:138)
	at java.base/java.lang.Thread.run(Thread.java:1474)

JavaTest Message: Test threw exception: java.lang.Exception: 1 errors found
JavaTest Message: shutting down test

STATUS:Failed.`main' threw exception: java.lang.Exception: 1 errors found
----------rerun:(39/10118)*----------
Comments
The fix for this issue is integrated in jdk-26+4-271.
23-06-2025

[~rriggs] This is failing in every tier2 run so needs attention.
22-06-2025

This is caused by RMI's multiplex protocol removal not updating the specification Table of Contents. Updated issue title accordingly.
20-06-2025