I've filed https://bugs.openjdk.java.net/browse/JDK-8210985.
Thanks for looking into this.
Paul
On 9/17/18, 8:37 AM, "Sean Mullan" wrote:
On 9/12/18 2:25 PM, Hohensee, Paul wrote:
> Thanks very much for investigating. We're aware that the cache size can
be set by the user, but many o
On 9/12/18 2:25 PM, Hohensee, Paul wrote:
Thanks very much for investigating. We're aware that the cache size can be set
by the user, but many of our users haven't done so because it hasn't been
necessary, and boom.
Would you mind filing a bug and we will look into it?
Thanks,
Sean
Paul
Thanks very much for investigating. We're aware that the cache size can be set
by the user, but many of our users haven't done so because it hasn't been
necessary, and boom.
Paul
On 9/11/18, 12:49 PM, "core-libs-dev on behalf of Sean Mullan"
wrote:
Hi Paul,
Thank you for bring
Hi Paul,
Thank you for bringing this issue to our attention. While we agree that
this does indeed seem like an issue that should be addressed, it is
quite late in the JDK 11 schedule, and it does not appear to be a new
issue introduced in JDK 11. We will be investigating this offline and
will
cross-posting to security-dev since this is related to SSL/TLS.
On 9/11/18 11:41 AM, Hohensee, Paul wrote:
The default value for the maximum number of entries in the SSL session cache
(which is a SoftReference cache) is infinite, and the entry timeout is 24
hours. With larger heaps, we’re runn
