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 2013/07/21 01:20:48 UTC
[jira] [Resolved] (LOG4J2-318) On termination Log4j terminates
before the application
[ https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers resolved LOG4J2-318.
--------------------------------
Resolution: Fixed
Fix Version/s: 2.0-beta9
Add shutdownHook attribute to the configuration element. If set to "disable" then no shutdown hook will be registered.
> On termination Log4j terminates before the application
> ------------------------------------------------------
>
> Key: LOG4J2-318
> URL: https://issues.apache.org/jira/browse/LOG4J2-318
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.0-beta8
> Reporter: Maurizio Sartori
> Assignee: Ralph Goers
> Labels: shutdown
> Fix For: 2.0-beta9
>
> Attachments: test.zip
>
>
> My application is multi-threaded, when Ctrl-C is pressed to terminate it, Log4J ShutdownHooks in LoggerContext are called to close the appenders, so I lost any log that the application does during its termination.
> What I think I need, is a way to disable the automatic close done by LoggerContext and a way to call the close by myself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org