RE: [OT] Re: log4j.properties file co-opting container logging. - Found word(s) optin in the subject
At 08:19 AM 9/30/2004 +0100, you wrote: -Original Message- From: Jacob Kjome > Do you know what logger is used by default by commons-logging in > Tomcat if log4j isn't present? > I'm not very privy to the internals of commons-logging, but I think they have some sort of simple logger which is used when there is no other logging implementation available. Don't quote me on that, though. Is it the commons-logging that produces catalina_log.date.txt? Is there a config file as per log4j? Even when testing, this file becomes quite significant. It would be nice to reduce/minimise its output. Ultimately, Tomcat uses commons-logging for logging, but uses its own Logger interface which is configured in context configuration files or server.xml. Note that this is no longer the case in 5.5.x. Read the docs on Tomcat's Logger's for more info. Jake - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [OT] Re: log4j.properties file co-opting container logging. - Found word(s) optin in the subject
-Original Message- From: Jacob Kjome > Do you know what logger is used by default by commons-logging in > Tomcat if log4j isn't present? > I'm not very privy to the internals of commons-logging, but I think they have some sort of simple logger which is used when there is no other logging implementation available. Don't quote me on that, though. Is it the commons-logging that produces catalina_log.date.txt? Is there a config file as per log4j? Even when testing, this file becomes quite significant. It would be nice to reduce/minimise its output. regards DaveP ** snip here ** -- DISCLAIMER: NOTICE: The information contained in this email and any attachments is confidential and may be privileged. If you are not the intended recipient you should not use, disclose, distribute or copy any of the content of it or of any attachment; you are requested to notify the sender immediately of your receipt of the email and then to delete it and any attachments from your system. RNIB endeavours to ensure that emails and any attachments generated by its staff are free from viruses or other contaminants. However, it cannot accept any responsibility for any such which are transmitted. We therefore recommend you scan all attachments. Please note that the statements and views expressed in this email and any attachments are those of the author and do not necessarily represent those of RNIB. RNIB Registered Charity Number: 226227 Website: http://www.rnib.org.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
