[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714429#comment-13714429
]
Gary Gregory commented on LOG4J2-318:
-------------------------------------
I do not like having to tweak the command line, everything should be done in
the config file, even JMX. Sure, you can have command line gadgets if you like
but only to _override_ the config file.
> 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
> Labels: shutdown
> 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: [email protected]
For additional commands, e-mail: [email protected]
