Re: about JDK-8186628

Thanks for your explanation. I worked on a lot of early java code circa Java 1.2 - 1.4, converting it to the post Java 5 memory model. Latent race conditions caused hundreds of bugs, and problems would occur in other unrelated parts of the code, it was very brittle, any changes to code

Re: about JDK-8186628

Hi Peter, On 04/21/18 10:42, Peter wrote: I wrote caching software that decorated any Java collection with soft, weak, timed or strong references, it utilised a background thread to clean references from underlying collections. It was non blocking if the underlying collection was, although

Re: about JDK-8186628

I wrote caching software that decorated any Java collection with soft, weak, timed or strong references, it utilised a background thread to clean references from underlying collections. It was non blocking if the underlying collection was, although it hasn't been updated to Java 8.

Re: about JDK-8186628

I'll go ahead with a review of the enhancement request JDK-8202086 shortly on this list. And we'll still need to decide what has to be done in the earlier releases of JDK. With kind regards, Ivan On 4/20/18 10:06 AM, nezih yigitbasi

Re: about JDK-8186628

Ivan, thanks for the information. Any ideas about when one of these solutions can be released? Nezih 2018-04-20 9:22 GMT-07:00 Ivan Gerasimov : > Hello Nezih! > This issue is still being discussed off-list. > There have been two approaches proposed so far: 1) improve

Re: about JDK-8186628

Hello Nezih! This issue is still being discussed off-list. There have been two approaches proposed so far: 1) improve the session cache and 2) provide an option to turn the cache off completely. The former one is good by itself, so I filed an enhancement request [1] with a link to proposal