JDK-8224589 : Improve startup behavior of SecurityProperties
- Type: Enhancement
- Component: security-libs
- Sub-Component: java.security
- Affected Version: 11,13
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-05-22
- Updated: 2019-10-04
- Resolved: 2019-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.
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 13 |
|---|---|
| 11.0.5-oracleFixed | 13 b22Fixed  |
Description
Some java.security properties will always be accessed even when there's no SecurityManager installed, which means we might load sun.security.util.SecurityProperties early in the bootstrap sequence. To improve startup - and keep it from regressing in a few key applications - we should avoid calling through AccessController when there's no SecurityManager installed. Desugaring the lambda use here was also considered, but if we run with a SecurityManager installed we'll instantiate a few other lambdas during bootstrap so gain was not measurable.
Comments
|