[
https://issues.apache.org/jira/browse/LOG4J2-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13714523#comment-13714523
]
Ralph Goers commented on LOG4J2-318:
------------------------------------
I am adding the configuration to allow disabling the shutdown hook. The JMX
configuration should be in a separate Jira issue. I am also adding code to
handle an IllegalStateException, which can occur when something tries to create
a LoggerContext during JVM shutdown.
I don't believe code any more code is needed to call shutdown. The user can
currently do
{code}
org.apache.logging.log4j.core.LoggerContext context =
(org.apache.logging.log4j.core.LoggerContext)LogManager.getContext(false);
context.stop();
{code}
I don't believe shutdown should be part of the Log4j public API but should be
part of the implementation, so the above is correct.
> 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
> 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]
