Details
-
Improvement
-
Resolution: Unresolved
-
Major
-
None
-
1.1.2
Description
Currently, the ContextDetachingSCL only supports detaching a ContextJNDISelector.
If some other ContextSelector implementation is used, it would be nice if the ContextDetachingSCL gracefully stopped logback as described in chapter 3 of the logback manual.
As a side effect, I think this type of implementation would provide the added benefit of gracefully stopping AsyncAppender instances instantiated as part of a web application context.
Attached is an updated ContextDetachingSCL implementation that detaches the default context if no context is found via a JNDI lookup.
Thoughts?