[ http://jira.qos.ch/browse/LBCLASSIC-141?page=com.atlassian.jira.plugin.syste... ] Ralph Goers commented on LBCLASSIC-141: --------------------------------------- I would suggest that this context listener should be combined with the context listener in the file uploaded in LBCORE-59 to allow configuration changes to be detected.

ContextListener that stops the LoggerContext when using DefaultContextSelector ------------------------------------------------------------------------------

Key: LBCLASSIC-141 URL: http://jira.qos.ch/browse/LBCLASSIC-141 Project: logback-classic Issue Type: Improvement Affects Versions: 0.9.15 Reporter: Paul Nyheim Assignee: Logback dev list Priority: Minor Attachments: DefaultContextDetachingSCL.java

When using the "The simplest and easiest approach" to configure logback as described here: http://logback.qos.ch/manual/loggingSeparation.html, The LoggerContext never gets stopped when the application is redeployed in an applicationserver. This causes both memory leaks, and an unability to Rename log files using RollingFileAppender because several handles to the log file exists. An easy solution to this is to stop the LoggerContext in a ServletContextListener - much the same as for the ContextJNDISelector using ContextDetachingSCL. I will upload a file - based on the ContextDetatchingSCL which does the job.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira