logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-658) shutdown hook called too early
Date Fri, 22 Aug 2014 23:10:12 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14107660#comment-14107660

Ralph Goers commented on LOG4J2-658:

Things like the HTMLLayout, XMLLayout, or JSONLayout will not have the appropriate footer
content written if their stop method isn't called. Most other things will probably be OK.
After all, I don't think Log4j 1.x has support for shutdown and it has been used for years.

> shutdown hook called too early
> ------------------------------
>                 Key: LOG4J2-658
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-658
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0-rc1, 2.0-rc2, 2.0.2
>            Reporter: Romain Manni-Bucau
>            Assignee: Matt Sicker
> Hi
> this issue follow few mail exchanges from the commons list. Here the interesting part
for log4j2:
> {quote}
> Here what I do (we can move it to another thread since that's 100% log4j2 related): 
> unzip apache-tomee-1.7.0-SNAPSHOT-webprofile.zip && 
> cd apache-tomee-webprofile-1.7.0-SNAPSHOT/ && 
> rm conf/logging.properties  && 
> echo 'openejb.log.factory=log4j'>conf/system.properties && 
> cp ~/log4j2.xml conf/log4j2.xml && 
> cp ~/.m2/repository/org/apache/logging/log4j/log4j-api/2.0-rc2-SNAPSHOT/log4j-api-2.0-rc2-SNAPSHOT.jar
lib/ && 
> cp ~/.m2/repository/org/apache/logging/log4j/log4j-core/2.0-rc2-SNAPSHOT/log4j-core-2.0-rc2-SNAPSHOT.jar
lib/ && 
> cp ~/.m2/repository/org/apache/logging/log4j/log4j-1.2-api/2.0-rc2-SNAPSHOT/log4j-1.2-api-2.0-rc2-SNAPSHOT.jar
lib/ && 
> ./bin/catalina.sh
> it makes server starting with log4j2 logs, if you ctrl+c logs are not printed. Sure it
is cause context is closed too early and then loggers have NullConfiguration. (If I debug
in java.lang.ApplicationShutdownHooks#runHooks to wait all hooks exec it works)
> {quote}
> Basically the issue is that when shutting down with ctrl+C some logs are swallowed.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message