[ http://jira.qos.ch/browse/LBCLASSIC-228?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu resolved LBCLASSIC-228. ---------------------------------- Fix Version/s: 0.9.28 Resolution: Won't Fix Although a very interesting and probably useful feature, I think it would require a very big effort to implement. In the mean time I am marking this bug as WONT FIX.
Revert to previous configuration if configuration fails during scan -------------------------------------------------------------------
Key: LBCLASSIC-228 URL: http://jira.qos.ch/browse/LBCLASSIC-228 Project: logback-classic Issue Type: Improvement Affects Versions: 0.9.26 Reporter: Simon Kelly Assignee: Ceki Gulcu Priority: Critical Fix For: 0.9.28
With logback configured to scan for changes in the config file, if the change causes an error in the configuration (e.g. syntax of undefined property) the logger remains unconfigured and does not perform any future scans. The only way to reconfigure the logger is to restart the applicaiton (in the case of a webapp). It would be good for logback to be able to recover from such an error by reverting to the previous configuration so that logging continues and also the error in the config file may be fixed.
-- 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