RFR: 8060132: Handlers configured on abstract nodes in logging.properties are not always properly closed
mandy.chung at oracle.com
Fri Oct 24 18:31:50 UTC 2014
On 10/10/2014 8:39 AM, Daniel Fuchs wrote:
Sorry for the delay. I have been pondering if there is a better
alternative and looks like you have considered a few other options that
none of them is a good one.
Is this only problem to the abstract node of Loggers (i.e. the ancestor
is in the logging configuration but the library/app never creates such
Your patch will keep all loggers defined in the configuration strong
reference. What if the application really wants the loggers say
com.foo.FooLogger to get GC'ed (e.g. it wants the logger class and
its defining class loader to be garbage collected) but the configuration
does name com.foo.FooLogger.handler = ....
Would that cause memory leak?
More information about the core-libs-dev