RFR: 8223260: NamingManager should cache InitialContextFactory
daniel.fuchs at oracle.com
Wed Feb 5 16:51:57 UTC 2020
On 05/02/2020 15:31, Peter Levart wrote:
>> I think this is about allow the InitialContextFactory instance to be
>> GC'ed when the thread is long lived. It might not be a concern for the
>> LDAP or the other providers in the JDK.
> Ah, I see. You mean when the ClassLoader is long lived. So this is a
> normal matter of trying to release the InitialContextFactory and objects
> held by it when there is a memory pressure and not the matter of
> avoiding class loader leaks? In this case it would pay only if
> InitialContextFactory holds more memory than SoftReference itself...
> Regards, Peter
Yes the concern is that the InitialContextFactory would be kept around
until the ClassLoader itself is GC'ed, even if the factory was used once
and not needed anymore. Could that become an issue in case the factory
is loaded e.g. by the System ClassLoader?
But it's a good point that it might not be a concern if the
InitialContextFactory instance in itself doesn't retain much memory.
More information about the core-libs-dev