Hm, Sorry that this is kinda straying into log4j territory now. Adding the following to my web application log4j.properties
log4j.logger.org.apache.catalina=debug, R starts to yield _some_ logging, e.g 2004-08-12 15:23:34,283 - DEBUG (org.apache.catalina.session.StandardManager:653) - Force random number initialization completed 2004-08-12 15:23:34,283 - DEBUG (org.apache.catalina.session.StandardManager:653) - Force random number initialization completed 2004-08-12 15:23:34,283 - DEBUG (org.apache.catalina.session.StandardManager:359) - Start: Loading persisted sessions 2004-08-12 15:23:34,283 - DEBUG (org.apache.catalina.session.StandardManager:359) - Start: Loading persisted sessions Although why there is 2 of everything I have no idea. What I am really interested in is the logging from log4j.logger.org.apache.catalina.load so I can see what class is being loaded when ThreadDeath occurs. I'm going to try and look at this problem if I can but this is my first ever look at Tomcat source so I am hopeful but not optimistic ;) I tried adding a log4j.properties and log4j jar to commons/lib as the FAQ suggests to get TC logging but no new log is created and no logging of the load package happens (boo). Do TC developers not have the logging switched on when developing? Allistair Crossley New Media Group, QAS Ltd Telephone: 020 7819 5343 > -----Original Message----- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: 12 August 2004 13:43 > To: Tomcat Users List > Subject: RE: Debugging Tomcat > > > Hi, > > >1) Everywhere in the documentation on Tomcat and in the comments for > >server.xml, when the debug attribute is discussed, it will always say > "a > >higher number means more output". I find this statement reasonably > >confusing. It raises quite a lot of questions about what the maximum > number > >is and what that translates to in terms of logging output. > > The number is from 0-99, 0 meaning no logging and being the > default, 99 > meaning all the logging the component can generate *via that > mechanism*. > Which brings us to our next point, that most Tomcat logging > is now done > via commons-logging. To configure Tomcat's logging via > commons-logging, > see > http://jakarta.apache.org/tomcat/faq/misc.html#commonsLoggingLog4j. > > >(log.isLogEnabled()) statement. I would like to know which log this > >translates to, and how to enable it. > > Those are from commons-logging. The "log" variable is an instance of > org.apache.commons.logging.Log corresponding to the class' logger. > > >I have tried setting ALL debug attributes within server.xml to 4 but > this > >does not yield the logging statements I am looking for from (2). > > Read the above FAQ entry, then set org.apache.catalian = DEBUG in the > logging configuration file, and set debug="99" for all components in > server.xml that support that attribute. That's the most > logging you're > going to get. > > Yoav Shapira > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > <FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE> ------------------------------------------------------- QAS Ltd. Developers of QuickAddress Software <a href="http://www.qas.com";>www.qas.com</a> Registered in England: No 2582055 Registered in Australia: No 082 851 474 ------------------------------------------------------- </FONT> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
