JDK-7093090 : Reduce synchronization in java.security.Policy.getPolicyNoCheck
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 Availabitlity Release.
java.security.Policy.getPolicyNoCheck() is synchronized which causes some thread contention.
verified with 8 113 on the following combinations:
windows7 with IE and Firefox
Solaris Sparc 9 and 10 with Mozilz and Firefox
RHEL with Mozilla and FF
Sean, Can't find this bug JDK-642631, you mean is JDK-6424631? Which test should be run?
Yes, try running the applet in JDK-6424631.
To verify the fix, you could try running the test in JDK-642631, which this fix also addressed.
written to sean for more details to verify this bug
The fix involved adding an initialized flag to indicate when the system-wide
policy has been initialized and storing both the flag and the Policy object in
an AtomicReference. Then, I also used the double-check locking idiom to avoid
locking the Policy class when the Policy had already been initialized.