Re: Logging problem on Mandrake

2005-03-20 Thread Jacob Kjome
Is Log4j in WEB-INF/lib or is it only in CATALINA_HOME/common/lib? If the latter, and if you are manually configuring Log4j upon each webapp load, then you will be re-configuring the same logger repository multiple times in the default logger repository; the one which the server itself is usin

Re: Logging problem on Mandrake

2005-03-16 Thread James Stauffer
You could add -Dlog4j.debug and the it should print to standard output when it is being configured. It may also have other clues to help you. On Wed, 16 Mar 2005 14:54:27 +, John Hunsley <[EMAIL PROTECTED]> wrote: > It was deployed with a war file, when I boot tomcat I changed the > webapp

Re: Logging problem on Mandrake

2005-03-16 Thread John Hunsley
It was deployed with a war file, when I boot tomcat I changed the webapp dir to ROOT but whilst the app is running the war file doesnt re-deploy so I guess it is not reloading. John. James Stauffer wrote: It is possible that your web app is being reloaded? Each reload could cause it to be con

Re: Logging problem on Mandrake

2005-03-16 Thread James Stauffer
It is possible that your web app is being reloaded? Each reload could cause it to be configured again. On Wed, 16 Mar 2005 13:24:29 +, John Hunsley <[EMAIL PROTECTED]> wrote: > Yes I get the same in txttools-web.log. I guess it is auto configured as > I just followed the instructions and cre

Re: Logging problem on Mandrake

2005-03-16 Thread John Hunsley
Yes I get the same in txttools-web.log. I guess it is auto configured as I just followed the instructions and created the log4j.properties file. I have made sure I do not call anything other than ; logger.warn(); or, if(logger.isDebugEnabled() ) logger.debug(); in my code, I do not set logging

Re: Logging problem on Mandrake

2005-03-15 Thread James Stauffer
Are the logs duplicated in txttools-web.log? Are you possibly sending logs to the console appender multiple times (at multiple levels)? Is it automatically configured or do you call code to tell it to use your log4j.properties? This sounds like it is being configured multiple times. On Tue, 15

Re: Logging problem on Mandrake

2005-03-15 Thread John Hunsley
This happens on any logging statement, log4J is configured through Log4j.properties, the file loks like this; log4j.rootLogger=DEBUG, console , file log4j.appender.file=org.apache.log4j.FileAppender log4j.appender.file.File=txttools-web.log log4j.appender.file.layout=org.apache.log4j.PatternLayou

Re: Logging problem on Mandrake

2005-03-15 Thread James Stauffer
Are you reloading any web apps? How are you configuring log4j? On Tue, 15 Mar 2005 14:51:31 +, John Hunsley <[EMAIL PROTECTED]> wrote: > Hi there, > > Im running an app in Tomcat5.0 on Mandrake 10.1. my logging statements > seem to grow over time. When I boot up tomcat the logging statements

Logging problem on Mandrake

2005-03-15 Thread John Hunsley
Hi there, Im running an app in Tomcat5.0 on Mandrake 10.1. my logging statements seem to grow over time. When I boot up tomcat the logging statements for each thread are displayed in catalina.out as they should, but after a while each statement prints out two or three times, the thread number a