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]
