[
https://issues.apache.org/jira/browse/LOG4J2-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14381111#comment-14381111
]
Frédéric Poliquin commented on LOG4J2-868:
------------------------------------------
Is it possible that this feature introduced a memory leak? I see a jvm shutdown
hook (DefaultShutdownCallbackRegistry) holding a reference to my webapp
classloader after I undeployed. This is causing a permgen out of memory error
after many deploy/undeploy cycles.
There doesn't seem to be any ways to remove the hook even if I close the
logging context. Log4j2 is packaged inside the war.
I don't have any control over the system properties that get set at startup so
I cannot disable the functionnality...
> Allow shutdown hook registration handling to be customizable
> ------------------------------------------------------------
>
> Key: LOG4J2-868
> URL: https://issues.apache.org/jira/browse/LOG4J2-868
> Project: Log4j 2
> Issue Type: New Feature
> Components: Core
> Affects Versions: 2.0.2
> Reporter: Matt Sicker
> Assignee: Matt Sicker
> Priority: Blocker
> Fix For: 2.1
>
>
> Besides the ability to enable or disable the shutdown hook, there should be a
> ShutdownRegistrationStrategy interface for customizing how to register a
> shutdown callback in LoggerContext. This will allow application servers to
> specify their own class that can register the shutdown callback for a
> LoggerContext.
> To make this really flexible, Log4jContextFactory should be the class that
> creates the ShutdownRegistrationStrategy.
> The basic idea behind this feature is already implemented. I'd like to make
> this API a bit better before 2.1 so we aren't stuck with a useless interface
> later on.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
