Lifecycle stop() method is never called

Ceki Gulcu added a comment - 19/Oct/10 11:11 PM Hello Lieven, What is the object type on which you would stop() to be called?

Ralph Goers added a comment - 20/Oct/10 5:30 AM I happened to notice this as I was writing a routing appender similar to what we discussed in another Jira issue over the weekend. I was surprised to see that LoggerContext doesn't contain the list of configured appenders. It occurred to me that since appenders are started as they are created that if an appender is never referenced by a logger it will never be stopped. I would imagine this is fairly common since loggers are often commented out and then readded when more log output is desired. It also occurred to me that this means that if multiple loggers reference the same appender that the appender will be stopped when the first one stops its appenders even though it is still attached to multiple loggers. The consequence of this is that although logback is threadsafe during a reconfiguration the state of logging is unpredictable during that time.