Robin Jansohn created LOG4J2-1098:
-------------------------------------
Summary: log4j.shutdownHookEnabled=false from log4j-web ignored?
Key: LOG4J2-1098
URL: https://issues.apache.org/jira/browse/LOG4J2-1098
Project: Log4j 2
Issue Type: Bug
Components: Web/Servlet
Affects Versions: 2.3
Reporter: Robin Jansohn
In the documentation it says:
Overrides the global flag for whether or not a shutdown hook should be used to
stop a LoggerContext. By default, this is enabled and can be disabled on a
per-configuration basis. When running with the log4j-web module, this is
automatically disabled.
I included the log4j-web module into my Maven project so the shutdown hook
should be disabled. During initialization I can see in the debug messages that
this is not the case:
DEBUG Starting LoggerContext[name=31484215] from configuration at null
DEBUG Starting LoggerContext[name=31484215,
org.apache.logging.log4j.core.LoggerContext@1836523] with configuration
XmlConfiguration[location=C:\app\apache-tomcat-8.0.24\wtpwebapps\webapp\WEB-INF\classes\log4j2.xml]...
DEBUG Shutdown hook enabled. Registering a new one.
DEBUG Starting configuration
XmlConfiguration[location=C:\app\apache-tomcat-8.0.24\wtpwebapps\webapp\WEB-INF\classes\log4j2.xml]
[...]
During shutdown (more specifically the contextDestroyed method of the
ServletContextListener) I try to log some messages but the Logger is already
shut down and therefore swallows all log messages (see LOG4J2-658).
Do I need to do something else to disable the shutdown hook?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
