JDK-8255603 : Memory/Performance regression after JDK-8210985
- Type: Bug
- Component: security-libs
- Sub-Component: javax.net.ssl
- Affected Version: 11.0.5,15,16
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-10-29
- Updated: 2021-04-12
- Resolved: 2020-11-01
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 | JDK 15 | JDK 16 | JDK 8 | Other |
|---|---|---|---|---|---|
| 11.0.10-oracleFixed | 13.0.6Fixed | 15.0.2Fixed | 16 b23Fixed  |
8u281Fixed |
openjdk8u282Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
It seems that there exists a memory/performance regression that was introduced with JDK-8210985: Update the default SSL session cache size to 20480. The idea to limit the maixmum SSL session cache size by itself is good. Unfortunately, as per the current implementation of sun.security.util.MemoryCache, it also modifies the initial size of the LinkedHashMap that is backing the cache to initialize with more than the maximum size.
Comments
|