Well I'm looking at 3 appenders and 3 loggers for each project. I have roughly 200 projects. I am looking for any idea's on how to best scale my log4j.xml file to handle this. I bought the commercial manual but I don't see anything mentioned about how I could go about making mini configurations and include them all into the log4j.xml file. I am open to any suggestions!
-----Original Message----- From: Curt Arnold [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 29, 2005 9:33 AM To: Log4J Users List Subject: Re: Error using NullAppender in <root> On Jun 29, 2005, at 8:59 AM, Schuweiler, Joel J. wrote: > You're kidding right? I say it works because, well, and this is a > toughie, it works. I just wanted to find out what was causing the > error. One of the design principles was that log4j should not introduce new failure modes for applications that use it. So if something goes wrong, a configuration files is missing or invalid, a file appender points to a non-existent location or is read-only, log4j doesn't stop the application from working. The downside of that is that problems with configuration files or other log4j-related problems are obscured. In this case, the xml configuration file was invalid according to the DTD, a message to that effect was output to the console, but log4j trooped on. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
