Re: config file reloading

2003-08-28 Thread Jacob Kjome
I used to use the configureAndWatch() method in my webapps, but I advise against it now. The watchdog classes currently have no lifecycle control. LogManager.shutdown() will *not* end the thread that the watchdog uses. If you try to reload your servlet context, the thread will continue to

Behaviour in Log4j when Logfile is deleted.

2003-08-28 Thread Raveendranath, Rohith (LNG - AUS)
Hi all, I am using Lo4j 1.2.8, During the cource of my application running i deleted the log file. Now there is no exception/error thrown. The application keeps on running ,possibly ignoring the logging part. Whys is this behaviour happening, Thanks and regards Rohith This e-mail is for

Re: config file reloading

2003-08-28 Thread Jacob Kjome
Oh, and I forgot to mention setting the -Dlog4j.configuration system property which you can poll to find where log4j.xml exists. Jake At 06:09 PM 8/27/2003 -0500, you wrote: I used to use the configureAndWatch() method in my webapps, but I advise against it now. The watchdog classes

RE: Log file location

2003-08-28 Thread sriram
The properties file is not being read at all I placed it in WEB-INF/classes. Still it's not being read. I am JBoss and JBoss contains log4j.jar by default and it has log4j.xml in default/conf folder. Probably even my application is taking log4j.xml from that location by default. I need to

RE: Log file location

2003-08-28 Thread Jacob Kjome
Hi Sriram, Do you have log4j.jar in WEB-INF/lib? If not, I'd expect default initialization not to work. Remember that the webapp class loader can see parent class loaders, but the parents cannot see the webapp class loader, hence your log4j.properties will definitely not be found. If you

RE: Log file location

2003-08-28 Thread sriram
Hi Jake, Thanks for the information. I have gone through the stuff you've written. Here's what I'm doing: 1. I placed log4j-1.2.8.jar in WEB-INF/lib 2. I placed log4j.properties in WEB-INF/classes 3. I deployed the application on JBoss 3.2.1 By default, JBoss has log4j.jar in jboss/lib which is

RE: Log file location

2003-08-28 Thread Ceki Gülcü
We should have a look at the jboss mailing lists. JBoss' class loader is called UnifiedClassLoader. The last time I look at UnifiedClassLoaders about a year ago, it seemed very smart. I'd have to look at the details again. At 02:05 AM 8/28/2003 -0500, Jacob Kjome wrote: Well, if you your app

Behaviour in Log4j when Logfile is deleted.

2003-08-28 Thread Raveendranath, Rohith (LNG - AUS)
Hi all, I am using Lo4j 1.2.8, During the cource of my application running i deleted the log file. Now there is no exception/error thrown. The application keeps on running ,possibly ignoring the logging part. Whys is this behaviour happening,should the log4j throw exception as its no longer

SizeBasedTriggeringPolicy $ TimeBasedRollingPolicy

2003-08-28 Thread Delfina Concepcion
Hi all! I'm getting started with log4j programming and i have my first doubt. I want a logger size based triggering policy and time based rolling policy so i'm using SizeBasedTriggeringPolicy and TimeBasedRollingPolicy in the following way: Logger root = Logger.getRootLogger();

Re: SizeBasedTriggeringPolicy $ TimeBasedRollingPolicy

2003-08-28 Thread Ceki Gülcü
Hello Delphina, TimeBasedRollingPolicy is somewhat special. It is declared as: public class TimeBasedRollingPolicy extends RollingPolicySkeleton implements TriggeringPolicy { } Thus, it combines both a rolling policy and a triggering policy. Look at the tests cases under

[HOWTO] DOMConfigurator in JBoss

2003-08-28 Thread Iwan
Hi, I'm trying to use the DOMConfigurator in a J2EE application that runs in Jboss 3.2.1. Since I want to configure the logging per application and have more than one application in a Jboss server running, I want a log4j-configuration.xml per .EAR file that defines the logging of that

RE: Log file location

2003-08-28 Thread sriram
Ceki, I'm trying the way you have mentioned at http://www.qos.ch/logging/sc.html (using LoggerRepository). In my java class, I have the following code: (I'm using JNDIRS you've mentioned in the above URL) private static final JNDIRS jndirs = new JNDIRS(); private static final LoggerRepository

RE: Log file location

2003-08-28 Thread Ceki Gülcü
Sriram, We have not yet added the code to automatically read configuration files when a repository is first accessed. However, nothing prevents you from configuring a repository in your applications. As for using and installing JNDIRS, JBoss has very cool ways for installing plugins. You might

RE: Log file location

2003-08-28 Thread sriram
Yes, I have done that and it's working. I have used log4j.xml of jboss (located in server/default/conf). I have added by own category in that: category name=com.mypackage priority value=ERROR/ /category So, all ERROR level messages generated in mypackage are written to server.log. But this

RE: Log file location

2003-08-28 Thread Ceki Gülcü
Yes, that is possible by using attaching an appender to com.mypackage and setting appender additivity to false. Please refer to log4j documentation at http://jakarta.apache.org/log4j/docs/documentation.html At 08:09 PM 8/28/2003 +0530, you wrote: Yes, I have done that and it's working. I

RE: Log file location

2003-08-28 Thread Jacob Kjome
At 06:27 PM 8/28/2003 +0530, you wrote: Ceki, I'm trying the way you have mentioned at http://www.qos.ch/logging/sc.html (using LoggerRepository). In my java class, I have the following code: (I'm using JNDIRS you've mentioned in the above URL) private static final JNDIRS jndirs = new JNDIRS();

RE: Log file location

2003-08-28 Thread Jacob Kjome
At 08:09 PM 8/28/2003 +0530, you wrote: I thought it would be a better idea to separate the application log with that of JBoss server log and so I am trying that out. But I wonder is there any way in which I can configure the following using JBoss's log4j.xml: - All server logs should be

Re: config file reloading

2003-08-28 Thread Larry Young
Jake, Thanks for the input and warnings! I can't use the -D option when starting tomcat because each webapp (~20 of them) will each have a separate configuration file. And the InitContextListener() will only work for my webapps, but not my standalone apps. So it would seem

Re: config file reloading

2003-08-28 Thread Larry Young
Jake, A quick question about your past use of configureAndWatch() ... I noticed in Ciki's book that when loading a config file, only those parts of the existing configuration which are explicitly mentioned in the new config file are affected. That makes sense if you are

Re: config file reloading

2003-08-28 Thread Jacob Kjome
Unfortunately, I don't have much to say here. I only ever added loggers. A better approach is to use a runtime logger configurator. There is one in the sandbox, but that only works on existing loggers. There are other runtime configurators out there that can add/remove loggers and

Re: config file reloading

2003-08-28 Thread Ceki Gülcü
Two short comments. 1) My name is Ceki not Ciki. 2) You can use LogManager.resetConfiguration() to reset or clear the existing config before you read the new config file. HTH, At 08:58 AM 8/28/2003 -0700, Larry Young wrote: Jake, A quick question about your past use of

Re: config file reloading

2003-08-28 Thread Jacob Kjome
At 06:16 PM 8/28/2003 +0200, you wrote: Two short comments. 1) My name is Ceki not Ciki. Sorry Ceki, typo. 2) You can use LogManager.resetConfiguration() to reset or clear the existing config before you read the new config file. Ah, yes. Never bothered with that since the configuration I do

Re: embedding chainsaw or logfactor5

2003-08-28 Thread Paul Smith
Hi Ricardo, On Thu, 2003-08-28 at 19:58, Ricardo Trindade wrote: Hi, I'm using logfactor5, and I'm wondering if it's possible to embed the logfactor5 or chainsaw swing panel inside my application. I can speak for Chainsaw, as one of the developers of it, I'll defer to someone else

Re: config file reloading

2003-08-28 Thread Larry Young
Ceki, At 06:16 PM 8/28/03 +0200, you wrote: Two short comments. 1) My name is Ceki not Ciki. apologies ... mea culpa!! 2) You can use LogManager.resetConfiguration() to reset or clear the existing config before you read the new config file. I think that is exactly what I was