[ https://jira.qos.ch/browse/SLF4J-192?page=com.atlassian.jira.plugin.system.i... ] Joachim Durchholz commented on SLF4J-192: ----------------------------------------- @Ralph Unfortunately, [https://issues.apache.org/jira/browse/LOG4J2-124] does not really argue why shutdown() would be a good idea. The discussion quickly diverges into the appropriate place to implement it. I hear that Log4J is both facade and implementation. If that's true, pointing at Log4J and saying that it has shutdown() isn't enough of an argument anyway: You also need to argue that it's in the facade part of Log4J, and that the association to that part was the correct decision. Feel free to complete that argument, but for now I'm staying unconcinved.
Need ability to shutdown loggers and flush appenders ----------------------------------------------------
Key: SLF4J-192 URL: https://jira.qos.ch/browse/SLF4J-192 Project: SLF4J Issue Type: Improvement Components: Core API Affects Versions: 1.6.x Environment: Operating System: All Platform: All Reporter: Michael Schall Assignee: SLF4J developers list
There needs to be a way to shutdown logging and flush async appenders so when a process is closing, all log events are written before the process is closed. Should ILoggerFactory have a shutdown or stop method? It could shutdown whatever logging back end I'm using? For log4j it would call - org.apache.log4j.LogManager.getLoggerRepository().shutdown(); For logback it would call - loggerContext.stop() Other back ends - ??? This is required to allow me to not reference logging back ends explicitly in my code to shutdown successfully without losing events. Discussion about this is happening on the user list at - http://www.qos.ch/pipermail/logback-user/2010-September/001816.html
-- This message was sent by Atlassian JIRA (v7.3.1#73012)