Write a little app to adjust debug levels on the fly. The basics of log4j are:
Logger lg = Logger.getLogger( "org.qi4j" ); lg.setLevel( Level.INFO ); 2 things to watch out for: 1. Clusters. 2. Classes are available in JVM only when loaded. So you will need a listing of them before you deploy the app. I do this @ build time. - Alex PS: I wish I could publish this app ... but I can not. The basic ideas are above. On Tue, May 19, 2009 at 1:39 PM, Borut Bolčina <borut.bolc...@gmail.com> wrote: > 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
