Ceki, Besides not locking up the entire hierarchy during the reset, I am also trying to avoid having log messages "lost" while the reset and configuration is being applied.
For example, let's say have the same logger referenced in the new configuration settings, with the same settings as current settings. And the code has been implemented to use the current resetConfiguration() method, called presumeably at the beginning of the parse() method. Then isn't it possible that logging messages will be "lost" in the time between the call to resetConfiguration() and the time when the (same) Logger settings are "reapplied"? By resetting only the Loggers that have not been referenced by the new configuration, at the end of configuration process, continuity is maintained, and no messages are lost. Does that make sense or is it too much tweaking? Is there another way I should approach this? thanks, -Mark -----Original Message----- From: Ceki Gülcü [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 19, 2002 4:21 PM To: Log4J Developers List Subject: Re: [CODE] Resetting Loggers during Configuration Hi Mark, Thanks for your contribution. Adding a new configuration directive such that a configurator resets the existing configuration is a good idea. Doing all sorts of the tricks in order to optimize the reset operation is not. Don't tune what you don't need to tune. Regards, Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
