I don't think you're going to find anything in log4j proper which can help you find out this type of information.
I believe that one of the major design goals for log4j was for the framework to fail gracefully, and not have logging errors cause application errors - not to prevent an application from running just because the log file couldn't be found/opened/etc. -----Original Message----- From: ecmcn [mailto:[email protected]] Sent: Thursday, September 10, 2009 7:48 PM To: [email protected] Subject: Verifying initialization What are some common techniques for verifying Log4J startup and initialization completed successfully? For a specific example, if DOMConfigurator can't parse my XML config file I'll get errors to stdout but nothing that tells my code there was a problem. I tried checking for the existence of my Appenders, but it seems they're loaded asynchronously. I could loop and wait until they're all there, but it seems like I must be missing something obvious. Any best practices out there? thanks, Eric -- View this message in context: http://www.nabble.com/Verifying-initialization-tp25392804p25392804.html Sent from the Log4j - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- 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]
