JDK-8168423 : Test Task: Custom system class loader + security manager + malformed policy file = recursive initialization
  • Type: Task
  • Component: security-libs
  • Sub-Component: java.security
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2016-10-20
  • Updated: 2017-02-23
  • Resolved: 2017-02-09
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 10 JDK 9
10Fixed 9 b157Fixed
Related Reports
Relates :  
JDK-8168075 - Custom system class loader + security manager + malformed policy file = recursive initialization
Description
Please read JDK-8168075 for context. However, we can ignore the WLS scenario and duplicate this bug with a typo in the policy file.
Use the JDK-8168075 and check if backtrace is similar or conversely we are missing ill-formed cases.
Address all the missing test scenario for (Custom system class loader + security manager + malformed policy file)
Comments
Initial webrev submitted on 2nd DEC@ http://cr.openjdk.java.net/~ssahoo/8168423/webrev.00/ Here is the generic Logic behind generating all possible Test cases with different combination of policy file, class loader and module types. for(policyFile : {"NO_POLICY", "VALID", "MALFORMED"}) { for(classLoader : {"SystemClassLoader", "CustomClassLoader"}){ // It uses possible set of regular/modular jars to generate all possible Test cases in ���cp and ���module-path. for(clientModuletype : {"STRICT", "AUTO", "UNKNOWN"}) { for(classLoaderModuleType : {"STRICT", "AUTO", "UNKNOWN"}) { Create and run java command line for each possible Test cases and verify result. } } } }
12-12-2016