[slf4j-dev] [JIRA] (SLF4J-192) Need ability to shutdown loggers and flush appenders
QOS.CH (JIRA)
noreply-jira at qos.ch
Thu Jan 3 17:26:00 CET 2019
[ https://jira.qos.ch/browse/SLF4J-192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19391#comment-19391 ]
Ondrej Zizka commented on SLF4J-192:
------------------------------------
One thing I don't understand: Quite a lot of people know how they would use such notification in the logger implementation. Some people don't. Well - those who do would use it, those who don't would not use it. What's the big deal? It's not cluttering the API since releasing the resources, and distributing the notification about when to do it, is inherent part of Java APIs since Java decision to get rid of destructors. I really wonder why anyone would oppose such part of an API.
> 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)
More information about the slf4j-dev
mailing list