Hello all, In "The complete manual - log4j" (Printed book) pages 80 - 82 go into great detail of how log4j handles reloading/reconfiguration. Specifically it documents how reloading a config file does not have the initially expected behavior of removing all original appenders, and then only setting up the new ones in the new file. This is ok, since it is well documented in the book.. But most of the time I would suspect that people would prefer the behavior of dropping all original appenders, and then creating all the new ones - so that only the new appenders exist after the config file is reloaded.
It would be great if this behavior could be implemented as well as the original behavior. This could be implemented by either an additional parameter to the configurators, or an additional method call before calling the configurators. It could also be implemented as an additional parameter in the configuration files... log4j.DumpAllAppenders = true. In this way we have the option of completely refreshing the configuration of log4j, without needing to be concerned with what the previous configuration of log4j was. Can this feature be added to log4j? I think this would work really well with my previous suggestion of having the log4j JMX write out the log4j config file, and then performing a reload of log4j. Later Rob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
