[
https://issues.apache.org/jira/browse/LOG4J2-868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286013#comment-15286013
]
Remko Popma commented on LOG4J2-868:
------------------------------------
[~yang_zhong] Thank you for reporting this problem.
Can you create a new JIRA ticket for this? (Since LOG4J2-868 is complete and
closed.)
We plan to release 2.6 very soon (in a few days).
It would be great if you could submit a patch or suggest a code change to
address this (in the new JIRA ticket).
Meanwhile, you can disable the shutdown hook in configuration with
{code}
<Configuration status="WARN" shutdownHook="disable">
...
{code}
> 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]
