I have seen this code used with configureAndWatch:
URL url = this.getClass().getResource("log4j.properties");
// Configure the properties and observe the file every 2 seconds
PropertyConfigurator.configureAndWatch(url.getPath(), 2000);But it is said to be problematic as it may cause issues with shutting down classloaders!? so that is why a configuration application is recommended. Peter ----- Original Message ----- From: "Borut Bolčina" <borut.bolc...@gmail.com> To: "List Tapestry User" <users@tapestry.apache.org> Sent: Tuesday, 19 May, 2009 14:39:07 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Changing logging level at runtime Hi, I've been using log4j's configureAndWatch in some of my backend java apps. I want to be able to change log4j.properties for my T5.0.18 web app and see the change (log level) in my logs without restarting Tomcat. My goal is to switch to debug level when I see "fishy behaviur" in the production deployed apps. How to achive this in best practice? -Borut --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
