[jira] [Created] (LOG4J2-658) shutdown hook called too early

["Romain Manni-Bucau (JIRA)" <ji...@apache.org>]

Romain Manni-Bucau created LOG4J2-658:
-----------------------------------------

             Summary: shutdown hook called too early
                 Key: LOG4J2-658
                 URL: https://issues.apache.org/jira/browse/LOG4J2-658
             Project: Log4j 2
          Issue Type: Bug
    Affects Versions: 2.0-rc1, 2.0-rc2
            Reporter: Romain Manni-Bucau


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
(v6.2#6252)

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