JDK-7169257 : Fix for 6424631 only partially ported to JDK 7 & JDK 8
  • Type: Bug
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: generic
  • CPU: generic
  • Submitted: 2012-05-16
  • Updated: 2012-05-22
  • Resolved: 2012-05-22
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 7 JDK 8
7u6Resolved 8Resolved
Related Reports
Relates :  
JDK-7093090 - Reduce synchronization in java.security.Policy.getPolicyNoCheck
Relates :  
JDK-6424631 - Signed applet hangs browser if a remote policy server is being used
Description
Whilst working on other bug fixes, I've noticed a discrepancy in the codebase between JDK families that doesn't make sense. Parts of the 6424631 fix are missing from JDK 7 & later even though the bug is marked fix integrated for JDK 7.

further investigation from Dev. team shows that : 

====
The changes in the deploy workspace, in AppletViewer.java, seem to have been ported from 6u1 to 1.7.0 b04.  However, the changes in j2se workspace, in src/share/classes/sun/security/jca/Providers.java, src/share/classes/sun/security/providers/PolicyFile.java, and src/share/classes/java/security/Policy.java do not appear in 1.7.0 b04 or any time later.

====

We meed to ensure this gets ported to avoid any potential regressions with people migrating from JDK 6 -> 7
Comments
EVALUATION After further testing and checks, it appears that this forward port is no longer needed for JDK7 or 8. The 7093090 changes which went into 7u4 have redesigned the getPolicyNoCheck() method and recursion should no longer be possible there given that we always exit getPolicyNoCheck() with a PolicyInfo with Policy!=null and an initialized value of true. Closing as not reproducible for this reason.
22-05-2012