-
Enhancement
-
Resolution: Fixed
-
P4
-
17, 21, 22
-
b10
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8329554 | 22.0.2 | Oli Gillespie | P4 | Resolved | Fixed | b02 |
| JDK-8328523 | 21.0.4 | Oli Gillespie | P4 | Resolved | Fixed | b01 |
| JDK-8333439 | 17.0.13 | Oli Gillespie | P4 | Resolved | Fixed | b01 |
where `constructorParameterClassName` is `java.security.SecureRandomParameters`. Doing this repeatedly is a waste of time/resources.
We can cache this lookup in EngineDescription itself. This covers not just SecureRandom, but also a few other Providers which take params (like CertStore).
In my experience, `new SecureRandom()` can be on an application's hot path. Users are reluctant to pool or share instances for fear of security and/or concurrency issues, plus more complex code.
- backported by
-
JDK-8328523 Avoid Class.forName in SecureRandom constructor
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk17u-dev/1ce0c635
-
Commit
openjdk/jdk21u-dev/eaa8ed99
-
Commit
openjdk/jdk22u/5cb863d2
-
Commit
openjdk/jdk/8ef918d6
-
Review
openjdk/jdk17u-dev/2310
-
Review
openjdk/jdk21u-dev/258
-
Review
openjdk/jdk22u/98
-
Review
openjdk/jdk/17559