I am having trouble understanding your quesiton. The LoggerContext.stop and LoggerContext.reset are closely related, except that the former also calls marks the LoggerContext as stopped. ContextDetachingSCL is only needed when a ContextSelector has been installed because in that case the LoggerContext instance in use can vary with the current application "context" as determined by the ContextSelector. HTH, On 28/12/2009 1:45 PM, Jeff Jensen wrote:
Is the answer that obvious I shouldn't ask?! ;-) If so, do the docs need updating?
-----Original Message----- From: logback-user-bounces@qos.ch [mailto:logback-user-bounces@qos.ch] On Behalf Of Jeff Jensen Sent: Thursday, December 10, 2009 1:40 PM To: logback-user@qos.ch Subject: [logback-user] LoggerContext.stop()
It seems the code in [1] and [2] do the same thing - call LoggerContext.stop(). Is this true (and therefore only need ContextDetachingSCL), or are both needed in a "thorough web app shutdown"?
[1] Section "Hot deploying applications" on page http://logback.qos.ch/manual/loggingSeparation.html
[2] Section "Avoiding memory leaks" http://logback.qos.ch/manual/jmxConfig.html#leak