Ok.
I found that  there is a library which has log4j.properties in the
classpath.
This library is used by our app.
Is there a way, that the log4j.xml is pulled from where I want rather
than the default classpath...

Thanks
Sudhendra (Sudhi) Seshachala
Office  : 281-514-0918
Cell    : 408-203-9960 
Mail to: [EMAIL PROTECTED]

-----Original Message-----
From: Jacob Kjome [mailto:[EMAIL PROTECTED] 
Sent: Thursday, December 23, 2004 2:50 PM
To: Log4J Users List
Subject: RE: Strange issue with log4j version 1.2.9

At 11:41 AM 12/23/2004 -0600, you wrote:
 > There is no other config file other than logger.xml.
 >I do write a java file Logger.java to manually configure logger.xml
>instead of default.
 >Nope. I do not need to specify the root logger level if I don't need
to  >  >All these are working, my only issue is that it creates an
additional  >RollingFileAppender file type called example.log on my
desktop. This is  >along with the configured log file...
 >

I still bet that somewhere, in some jar or other location on your
classpath, there is a log4j.properties or log4j.xml that is getting
picked up before you are performing manual configuration.  To test this,
change your config file to log4j.xml and put it in a directory that is
the first thing in the classpath.  I bet the other file doesn't get
created anymore.

Jake

 >Thanks
 >
 >Sudhendra (Sudhi) Seshachala
 >Office  : 281-514-0918
 >Cell    : 408-203-9960
 >Mail to: [EMAIL PROTECTED]  >  >-----Original Message-----
 >From: Jacob Kjome [mailto:[EMAIL PROTECTED]
 >Sent: Thursday, December 23, 2004 11:27 AM
 >To: Log4J Users List
 >Subject: Re: Strange issue with log4j version 1.2.9  >  >At 10:27 AM
12/23/2004 -0600, you wrote:
 >
 >>The logger.xml <<logger.xml>> has has a RollingFileAppender. With
file  >>name as c:\application_name-debug.log.
 >>But another file called example.log gets generated whenever I run the
>>application eventhough  I have not configured for this file anywhere..
 >>
 >>Can any one help me resolve this&.
 >
 >There is obviously another config file in your path which is getting
>used in autoconfiguration before it finds your config file.
 >There is
 > If you actually name your config file "logger.xml", then there is no
>way your file is getting picked up unless you manually configure log4j
>yourself.  Rename it to log4j.xml and make sure it is in the default
>package in the classpath.  I'm not even sure if your configuration will
>work without defining a <root> logger as the last entry in the file
>before </log4j:configuration> (in other words, I'm not sure if the
>DOMConfigurator will find it valid based on the dtd)?  Also, you should
>be using <logger> and <level>, not <category> and <priority>.  The
>latter have been deprecated in favor of the former.
 >
 >Hope that helps.
 >
 >Jake
 >
 >
 >---------------------------------------------------------------------
 >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]


---------------------------------------------------------------------
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]

Reply via email to