|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
I disagree that this is a duplicate.
My complaint is that calling loggerContext.reset() is not sufficient to stop the threads but I'd argue that it should be.
The current behavior contradicts the "clears all internal properties" part of the documentation at http://logback.qos.ch/apidocs/ch/qos/logback/classic/LoggerContext.html#reset%28%29
And I hope that this won't be fixed by adding "Potentially running thread pools will also survive a reset." to the javadoc. It's surprising enough that status messages survive a reset.