https://issues.apache.org/bugzilla/show_bug.cgi?id=49571
--- Comment #2 from David North <dtn-asfb...@corefiling.co.uk> 2011-10-06 16:29:35 UTC --- To expand a little on comment 1 ... the solution proposed in comment 0 would work, but it seems more risky to victimize a random log.debug/info call to do the work of checking if the config has changed and reloading it, since this may unexpectedly slow down whatever part of my app called the logger (and in the worst case, an exception might be raised as part of doing some logging). Polling for and applying log4j config changes is exactly the sort of thing a background thread should be used for; we just need to ensure that log4j makes an effort to shut down any threads it has started when LogManager.shutdown is called. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
