Jake, Your configuration is correct, however if your LogLog.debug messages are executed before you configure your logging system, your debug messages will not show up. The only messages that will show up (before your configure) are LogLog error
and warn messages. The config that you supply in your config file: <log4j:configuration xmlns:log4j='http://jakarta.apache.org/log4j/' debug="true" threshold="debug"> won't be read until you configure your log system, but the error and warn methods do not check this property in the config, so warn and error messages should show up. -----Original Message----- From: Jacob Kjome [mailto:[EMAIL PROTECTED]] Sent: Monday, June 10, 2002 7:03 PM To: Log4J Users List Subject: Re[4]: Logging while initializing config file question... Hello Marvin, hmmm.... I have my log4j.xml config file set up like: <log4j:configuration xmlns:log4j='http://jakarta.apache.org/log4j/' debug="true" threshold="debug"> I see all of log4j's internal statements, but I don't see any LogLog.debug(String) statements being printed out at all (that were being printed out before when I used System.out.println(), so I know I should be seeing the messages). Do I have to set LogLog programatically to get the output? If so, exactly what do I need to set and to what value? Jake Monday, June 10, 2002, 4:03:38 PM, you wrote: MC> If you want to log before your log system initializes, you can use MC> org.apache.log4j.helpers.LogLog methods error and warn. Log4j MC> uses these methods internally to print out log messages. Messages logged MC> using these methods will print out to console (System.err). Note that a MC> debug method is also available in the LogLog class, but it requires that you MC> configure the logging system as mentioned in a previous reply in order for MC> debug messages to be output. MC> Marvin MC> -----Original Message----- MC> From: Jacob Kjome [mailto:[EMAIL PROTECTED]] MC> Sent: Monday, June 10, 2002 2:31 PM MC> To: Log4J Users List MC> Subject: Re[2]: Logging while initializing config file question... MC> Thanks, that is good information that I didn't know. MC> However, what if I want to MC> put out my own messages within my init servlet. This is before any MC> calls to configure(). I do a bunch of checking to make sure that file MC> path passed to the servlet exists and whether the webapp is running MC> off the filesystem or directly from a .war file. MC> In that case, is my only option System.out.println(String)? MC> Jake MC> Monday, June 10, 2002, 1:11:53 PM, you wrote: TTM>> Assuming that you're using XMLConfigurator, you can use the following TTM>> adjuration in your config file: TTM>> <log4j:configuration xmlns:log4j='http://jakarta.apache.org/log4j/' TTM>> debug="true" threshold="debug"> TTM>> This will cause Log4j to issue log statements to System.out during TTM>> initialization and at some other occasions (e.g. when files roll etc). MC> Error TTM>> messages will be dumped to System.err irrespective of debug set to true MC> or TTM>> not. All Log4j messages to System err/out are prefixed with 'LOG4j:' TTM>> Hope this helps. TTM>> -- TTM>> Thomas TTM>> | -----Original Message----- TTM>> | From: Jacob Kjome [mailto:[EMAIL PROTECTED]] TTM>> | Sent: 10 June 2002 19:03 TTM>> | To: Log4J Users List TTM>> | Subject: Logging while initializing config file question... TTM>> | TTM>> | TTM>> | TTM>> | What does one do during configuration of Log4j? For instance, when TTM>> | one calls PropertyConfigurator.configure(file) or TTM>> | PropertyConfigurator.configureAndWatch(file), what kind of logging is TTM>> | available to see what is happening during this? Do you just bite but TTM>> | bullet and do System.out.println(String)? TTM>> | TTM>> | Jake TTM>> | TTM>> | TTM>> | -- TTM>> | To unsubscribe, e-mail: TTM>> | <mailto:[EMAIL PROTECTED]> TTM>> | For additional commands, e-mail: TTM>> | <mailto:[EMAIL PROTECTED]> TTM>> | TTM>> | TTM>> MC> ************************************************************************* TTM>> Copyright ERA Technology Ltd. 2002. (www.era.co.uk). All rights MC> reserved. TTM>> The information supplied in this email should be treated in confidence. TTM>> No liability whatsoever is accepted for any loss or damage TTM>> suffered as a result of accessing this message or any attachments. TTM>> MC> ________________________________________________________________________ TTM>> This email has been scanned for all viruses by the MessageLabs SkyScan TTM>> service. For more information on a proactive anti-virus service working TTM>> around the clock, around the globe, visit http://www.messagelabs.com TTM>> MC> ________________________________________________________________________ TTM>> -- TTM>> To unsubscribe, e-mail: MC> <mailto:[EMAIL PROTECTED]> TTM>> For additional commands, e-mail: MC> <mailto:[EMAIL PROTECTED]> -- Best regards, Jacob mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> *************************************************************** Confidentiality note: This e-mail contains information from the GFI Group Inc. and/or its affiliates, including GFInet inc., that is confidential and/or legally privileged. This information is intended only for the use of the individual or entity named on this e-mail. This e-mail and its content may not be reproduced or retransmitted without the express written permission of The GFI Group. *************************************************************** -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
