How can I ensure that logs don't get lost while configuring log4j. I'm using JDBCAppender and if DB2's bin directory is not in the library path, it fails. During the configuration process, I'm writing logs (this is in some common code that I use) to the logger. Until log4j is configured, these logs are going in the bit bucket. Is there any way for me to check if log4j has been configured/initialised and keep these logs in a queue to be logged after log4j comes up? Or at least print to the console?
Regards Milind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
