Re: Use of internal APIs to protect against memory leaks

2014-09-19 Thread Phil Race
> For the 2D disposer issue then 2d-dev is the place to start The 2d disposer has a call to Thread.setContextClassLoader(null) It's been there since JDK6u21 ... and is in all later releases. https://bugs.openjdk.java.net/browse/JDK-6936389 So there is no need I see for accessing this in JDK 9

Re: Use of internal APIs to protect against memory leaks

2014-09-19 Thread Alan Bateman
On 19/09/2014 14:12, Mark Thomas wrote: : The memory leaks stem from the generally more complex class loader structure present in a JavaEE container than is typically present in a standalone Java app. At this point, I have two questions. 1. Is this community interested in examining these memor

Use of internal APIs to protect against memory leaks

2014-09-19 Thread Mark Thomas
All, As you may know I am one of the Apache Tomcat committers. The Tomcat project was approached recently[1] to see what, if any, internal APIs Tomcat was using as part of the JDK 9 preparations. My response was that the only place Tomcat does this is in the memory leak prevention class [2]. I al