JDK-8267887 : RMIConnector_NPETest.java fails after removal of RMI Activation (JDK-8267123)
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 17
  • Priority: P5
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2021-05-27
  • Updated: 2024-07-25
  • Resolved: 2024-07-12
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 24
24 b07Fixed
Related Reports
Duplicate :  
JDK-8267888 - javax/management/remote/mandatory/connection/RMIConnector_NPETest.java fails after removal of RMI Activation
Relates :  
JDK-8267123 - Remove RMI Activation
Sub Tasks
JDK-8267886 :  
ProblemList javax/management/remote/mandatory/connection/RMIConnector_NPETest.java - Resolved
Description
The following test is failing after the integration of JDK-8267123, which removed RMI Activation:

javax/management/remote/mandatory/connection/RMIConnector_NPETest.java

This test has been problem-listed for the time being.

==========

#section:build
----------messages:(2/91)----------
command: build TestLibrary RMID
reason: User specified action: run build TestLibrary RMID
result: Not run. Test running...


test result: Error. can't find RMID in test directory or libraries 

==========
Comments
Changeset: f677b90e Branch: master Author: Kevin Walls <kevinw@openjdk.org> Date: 2024-07-12 08:19:24 +0000 URL: https://git.openjdk.org/jdk/commit/f677b90eb93026d3fdfd4ae19d48415a7d8318e8
12-07-2024
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/20054 Date: 2024-07-05 14:06:39 +0000
09-07-2024
<S12Y triage team>:ILW=LHL=P5
08-02-2022
The reason for the failure is that the test creates an instance of the RMID daemon, which is part of RMI Activation, and then it connects to it. RMID was removed as part of the RMI Activation removal (and so was the RMID test library class). From looking at the test, it doesn't appear to depend on any functionality of RMID itself; it just needs some RMI endpoint. Is that correct? If so, the test should be adjusted to create some other RMI endpoint, possibly rmiregistry, and connect to that instead of RMID. Redispatching to core-svc / javax.management for consultation. See me [~smarks] if there are any questions about RMI Activation or about my recommendations for this test.
27-05-2021