Re: Changing logging level at runtime

2009-05-19 Thread Paul Field
Tapestry users cc Subject Re: Changing logging level at runtime 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.

Re: Changing logging level at runtime

2009-05-19 Thread Peter Stavrinides
ssues with shutting down classloaders!? so that is why a configuration application is recommended. Peter - Original Message - From: "Borut Bolčina" To: "List Tapestry User" Sent: Tuesday, 19 May, 2009 14:39:07 GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subj

Re: Changing logging level at runtime

2009-05-19 Thread Thiago H. de Paula Figueiredo
On Tue, May 19, 2009 at 10:18 AM, Borut Bolčina wrote: > I am sure Tapestry offers simpler solution (configuring some service) or at > least offers the infrastructure to implement behind the scenes periodic > reading of the log4j configuration. > Does it? No. Tapestry doesn't even depends on log4

Re: Changing logging level at runtime

2009-05-19 Thread Borut Bolčina
I am sure Tapestry offers simpler solution (configuring some service) or at least offers the infrastructure to implement behind the scenes periodic reading of the log4j configuration. Does it? 2009/5/19 Alex Shneyderman > On Tue, May 19, 2009 at 2:33 PM, Borut Bolčina > wrote: > > Actually we

Re: Changing logging level at runtime

2009-05-19 Thread Alex Shneyderman
On Tue, May 19, 2009 at 2:33 PM, Borut Bolčina wrote: > Actually we do have this web app in cluster. in this case you will have to find out how to propagate level changes to all the instances of the cluster. > Are you saying that I should run this simple standalone java app to change > the log l

Re: Changing logging level at runtime

2009-05-19 Thread Borut Bolčina
Actually we do have this web app in cluster. Are you saying that I should run this simple standalone java app to change the log level of the web app? -Borut 2009/5/19 Alex Shneyderman > Write a little app to adjust debug levels on the fly. The basics of log4j > are: > > Logger lg = Logger.getL

Re: Changing logging level at runtime

2009-05-19 Thread Alex Shneyderman
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

Re: Changing logging level at runtime

2009-05-19 Thread Borut Bolčina
Tomcat 2009/5/19 Joachim Van der Auwera > use JBoss? > > > Borut Bolčina 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

Re: Changing logging level at runtime

2009-05-19 Thread Joachim Van der Auwera
use JBoss? Borut Bolčina 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

Changing logging level at runtime

2009-05-19 Thread Borut Bolčina
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