I don't know if this would work but you could try recursing the logger tree removing all appenders and reseting all levels before calling configure.
On 2/16/07, zeusfaber <[EMAIL PROTECTED]> wrote:
James Stauffer wrote: > > For one thing, DOMConfigurator.configure adds to the current config -- > it doesn't replace it. Thay is why some loggers still see the changed > configuration. > Thank you James for you prompt reply. Hummm, this could be the reason I'm seeing strange behaviours. But so, what would be the correct procedure to reload programmatically the old configuration without restarting the application? I found no evidence in the complete manual too :-) bye -- Davide -- View this message in context: http://www.nabble.com/Changing---Retrieving-log4j-config-at-runtime-tf3238396.html#a9007011 Sent from the Log4j - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- James Stauffer http://www.geocities.com/stauffer_james/ Are you good? Take the test at http://www.livingwaters.com/good/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
