There's two approaches. Configure tomcat to reload the context when class changes are made (log4j.properties being in the classes directory, will count as a class being changed, and then the whole context will reload). We do this all the time.
Log4j can be used in a manner where config changes are discovered at run-time, though I've never tried it (and you should ask about in on the log4j-user list) Mike Curwen > -----Original Message----- > From: Andy Kriger [mailto:[EMAIL PROTECTED] > Sent: Friday, January 21, 2005 12:03 PM > To: [email protected] > Subject: reload log4j.properties on-the-fly? > > > I am running Tomcat 5.5 with log4j logging (log4j.properties > in common/classes). > > Is it possible to make changes to the log4j properties and > have the changes reloaded on-the-fly instead of having to > restart Tomcat in order to pick up changes? This would be > very useful for those times debug level logging or specific > class logging is needed where generally that level of logging > is not required. > > thx > andy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
