1. We wrote a servlet filter that inspects the configuration periodically and resets the configuration if the file has changed. When running as a web app this will incur less overhead than the turbo filter. 2. The architecture of Logback is such that when a reconfigure occurs all the filters and appenders are removed first so it is almost guaranteed that events will be lost during a reconfiguration. I've been working on Log4J 2.0 which was designed to not have this design defect. Ralph On Jan 19, 2011, at 12:53 AM, Lars Fischer wrote:
Hello,
I'm investigating slf4j + logback, if it solves my requirements:
I need to change the logging configuration during application runtime and read the documentation about the config file scan.
Can this reconfiguration be done by my self without using the scan? More precisely: can I add and remove an own TurboFilter during runtime from my program code? How about logging events fired while applying these changes? Is it guaranteed, that no event will be lost?
Best regards, Lars _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://qos.ch/mailman/listinfo/logback-user