[slf4j-dev] [JIRA] (SLF4J-192) Need ability to shutdown loggers and flush appenders

QOS.CH (JIRA) noreply-jira at qos.ch
Sun Apr 22 06:39:00 CEST 2018

    [ https://jira.qos.ch/browse/SLF4J-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19168#comment-19168 ] 

Joachim Durchholz commented on SLF4J-192:

The code that has the direct dependency on the backend also knows why the backend needs a flush, and how to do it, so it can simply call that code wherever it would to the requested slf4j flush() call.

If the place that would do the flush() doesn't and shouldn't know about the backend in use, let the logger initialization framework supply a Runner, or a Consumer<ShutdownInfo>, or whatever java.util.function interface is best.

Flushing the backend is a real need, but SLF4J isn't the right messenger to relay the signal.

> 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

More information about the slf4j-dev mailing list