Questions about JDK-8136353 "ClassValue preventing class unloading"

2016-01-06 Thread Craig Andrews
I apologize for contacting this list - I'm sure this isn't the "right way" to contact the OpenJDK project, but I'm not clear what the "right way" is. I'm hoping to raise https://bugs.openjdk.java.net/browse/JDK-8136353 "ClassValue preventing class unloading" as I believe it's a significant

Re: Questions about JDK-8136353 "ClassValue preventing class unloading"

2016-01-06 Thread William ML Leslie
On 7 January 2016 at 07:34, Peter Levart wrote: > ClassValue API could use a different strategy and reference the cached > instance of type T from ClassValue instance instead, but then you would > have a problem with ClassValue instances reachable from other class loaders

Re: Questions about JDK-8136353 "ClassValue preventing class unloading"

2016-01-06 Thread Peter Levart
Hi Craig, I think that what you are asking for is impossible to achieve in current Java. ClassValue API is basically a cache that maps a pair: (ClassValue, Class) -> cached instance of type T You would like the cached instance of type T to not be reachable from either ClassValue instance

Re: Questions about JDK-8136353 "ClassValue preventing class unloading"

2016-01-06 Thread Peter Levart
On 01/06/2016 09:34 PM, Peter Levart wrote: Hi Craig, I think that what you are asking for is impossible to achieve in current Java. ClassValue API is basically a cache that maps a pair: (ClassValue, Class) -> cached instance of type T You would like the cached instance of type T to not