On 08/08/2016 11:20, Chris Hegarty wrote: > >> On 8 Aug 2016, at 08:51, Rory O'Donnell <rory.odonn...@oracle.com> wrote: >> >> Hi Mark, >> >> There are two fixes to bugs reported by you in b130, can you confirm fixes ? >> >> Early Access b130 <https://jdk9.java.net/download/> for JDK 9 is available >> on java.net, summary of changes are listed here >> <http://download.java.net/java/jdk9/changes/jdk-9+130.html>. >> >> 8156824 core-libs com.sun.jndi.ldap.pool.PoolCleaner should clear its >> context class loader >> 8157570 core-libs sun.rmi.transport.GC retains a strong reference to the >> context class loader
I can confirm that both these issues are resolved in Java 9 b130. For the benefit of those following the Tomcat dev list, the fix is not in: - Java 9, b129 ()jigsaw) - Java 8u112, b4 > With the two changes above, then several cleanups in > JreMemoryLeakPreventionListener::lifecycleEvent can be done in a JDK 9 > specific Tomcat source trunk. Otherwise, if the code needs to run on older > releases, it can be be made version specific, where it is not executed on > JDK 9 or greater. Tomcat 9 targets Java EE 8 which means it has to be able to run on Java 8. Therefore, given that the above issues will be fixed in the first Java 9 release, I intend to disable the protection if Java 9 is detected. > There is another of these unnecessary retention of the context class loader > issues, 8156841 [1], that I hope to address in a near future build of JDK 9. Excellent news. The other open issue I'm aware of related to the JreMemoryLeakPreventionListener is this one: https://bugs.openjdk.java.net/browse/JDK-8146961 I need to review the remaining things in JreMemoryLeakPreventionListener to see if any of them need to be raised as bugs. Thanks to everyone who has helped progress the fixes for these issues. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
