[jdk17u-dev] RFR: 8276660: Scalability bottleneck in java.security.Provider.getService()
duke
duke at openjdk.org
Thu Jul 25 20:48:34 UTC 2024
On Fri, 19 Jul 2024 18:46:32 GMT, Dan Lutker <dlutker at openjdk.org> wrote:
> Backporting [JDK-8276660](https://bugs.openjdk.org/browse/JDK-8276660) which also fixes a bug in SecureRandom registration that was exposed during testing of https://github.com/corretto/amazon-corretto-crypto-provider. Currently, if you register a new provider then `new SecureRandom` doesn't work right away and only after making some other call like `Cipher.getInstance()` does it return the ACCP provided SecureRandom.
>
> Ran all "java/security/Provider/", "jdk/jfr/event/" and tier1 tests locally on Linux x64 and they passed.
>
> "[JDK-8254711](https://bugs.openjdk.org/browse/JDK-8254711): Add java.security.Provider.getService JFR Event" makes changes some of the same functioned but was different in 17u than upstream. To get a cleaner backport I reverted it locally, backported [JDK-8276660](https://bugs.openjdk.org/browse/JDK-8276660) and then re-applied 8254711 to get the updated code around the Map changes.
>
> Also backporting the followup fixes:
> 8292739: Invalid legacy entries may be returned by Provider.getServic…
> 8279222: Incorrect legacyMap.get in java.security.Provider after JDK-8276660
@lutkerd
Your change (at version be1ae3ac53b9f5c72d9965d42df23adbda900b1e) is now ready to be sponsored by a Committer.
-------------
PR Comment: https://git.openjdk.org/jdk17u-dev/pull/2730#issuecomment-2251366776
More information about the jdk-updates-dev
mailing list