You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2014/10/15 17:15:34 UTC
[jira] [Resolved] (LOG4J2-868) Allow shutdown hook registration
handling to be customizable
[ https://issues.apache.org/jira/browse/LOG4J2-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-868.
--------------------------------
Resolution: Fixed
switched to defaultThreadFactory as suggested. It seems to be working fine.
> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org