JDK-8206865 : RMI activation tests fail with InvalidClassException
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.io:serialization
  • Affected Version: 11,12
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2018-07-07
  • Updated: 2018-08-09
  • Resolved: 2018-07-20
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 11 JDK 12
11 b24Fixed 12Fixed
Related Reports
Relates :  
Relates :  
Description
Five RMI activation tests failed after merging of JDK-8010319 / JEP 181: Nest-Based Access Control. All tests failed with same error, java.io.InvalidClassException: 

java/rmi/activation/ActivationSystem/modifyDescriptor/ModifyDescriptor.java,[tier3],[windows-x64],[Exception: java.io.InvalidClassException: sun.rmi.server.Activation$LogRegisterGroup; no valid constructorException: TestFailedException: TEST FAILED: Rmid process exited with status ... after ...ms.],[bug4127754 othervm], [ModifyDescriptor],[5421],[] 

The list of failed tests is as follows:

java/rmi/activation/ActivationSystem/modifyDescriptor/ModifyDescriptor.java
java/rmi/activation/Activatable/restartService/RestartService.java
java/rmi/activation/Activatable/restartCrashedService/RestartCrashedService.java
java/rmi/activation/Activatable/forceLogSnapshot/ForceLogSnapshot.java
java/rmi/activation/Activatable/checkRegisterInLog/CheckRegisterInLog.java
Comments
Added noreg-other because this fix will be covered by existing tests.
19-07-2018

Tests is now problem listed (via JDK-8207818) in JDK 11. Please remember to remove them from ProblemList.txt with this (JDK-8206865) fix.
19-07-2018