In order to detect previous configurations of log4j, log4j 1.3 will add a flag called "isPristine" to the logger repository. If the flag is set to true, you can assume that a given repository has not yet been configure.
At 06:50 PM 4/20/2004, you wrote:
I had the same exact problem with a 3rd party JDBC driver.
NCR's Terdadata JDBC driver was programmatically configuring Log4j loggers and appenders.
My workaround is described here:
http://www.theserverside.com/news/thread.tss?thread_id=21054
-Sean
> -----Original Message----- > From: Peake, Chris [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 20, 2004 9:27 AM > To: [EMAIL PROTECTED] > Subject: Messages getting redirected to non related log file > > > I have a program that logs messages to the console and a file using the > correct appenders. Works great, until I call a 3rd party tool that seems > to > be co-opting my logger somehow. As soon as that program is encountered, > ALL > MY messages start going to his log file and no longer to MY logfile. My > appenders are all named differently. > > I can't seem to find the root cause. > > I've tried various releases of log4j. >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Ceki G�lc�
For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
