I have found it to be fine. Obviously there must be a hit somewhere, but the value of its function outweighs anything I have seen. Especially when you have an environment that has developers who want to CHANGE EVERYTHING, NOW!
Luc "Denis McCarthy" <[EMAIL PROTECTED]> on 08/28/2002 09:32:12 AM Please respond to "Log4J Users List" <[EMAIL PROTECTED]> To: "Log4J Users List" <[EMAIL PROTECTED]> cc: Subject: Is PropertyConfigurator.configureAndWatch() expensive? Hi there, I'm thinking of making my log4j.properties file dynamically configurable by using configureAndWatch() in my application configuration. Prior to this I would like to ensure that it does not hog system resources in any way. Can anyone confirm that using configureAndWatch() does not lead to any appreciable system slowdown? Thanks Denis McCarthy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED] > For additional commands, e-mail: <mailto:[EMAIL PROTECTED] > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
