Everything about Java 8 →
A comprehensive summary of the developer-facing changes coming in Java 8.
A comprehensive summary of the developer-facing changes coming in Java 8.
The problem is a a classloader leak.
This is a specific type of a memory leak when classloaders cannot be unloaded (for example on Java EE application redeploys) and thus all the class definitions referenced by the classloader are left hanging in your permanent generation.
The Thread blocking our classloader to be garbage collected is referenced from the sun.net.www.http.KeepAliveCache instance field keepAliveTimer.
This issue is fixed in JDK 7.
“To cut a long story short:
A computer with a few GB of memory of non-ECC memory is likely to incur to several memory errors every year.
Users reporting isolated, impossible to understand and reproduce crashes, not using ECC memory, can’t be taken as a proof that there is a bug.”
Why hash spaces have to be huge to avoid collisions.