You'll get a better response by posting this to the appropriate list (namely [EMAIL PROTECTED]). This list is for communication between the developers of Log4j.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 9:59 AM To: [EMAIL PROTECTED] Subject: fail over Hi, there, I an new to Log4j. I need help to find out the best way to handle fail over in log4j. We are working on a critical application within which we use file for logging and database for audit. We can not afford to stop the application if there are errors with file system or database, nor can we afford to lose those logging/audit information. We plan to use a database to back up files if there is a problem with file system, and using files to back up database if something wrong with the database, but we don't want duplicate info on both file and database. I understand there are two ways to do this: (1) To specify a secondary appender in the errorHandler attached to the primary appender. e.g. if primary appender is a file, then the secondary appender is a database, or vice versa. (2)Dynamically remove the appender if error is detected with that appender, and add a new appender to the logger. Which way is better, and are there any other ways to do this? Thanks for the info. --Ling -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
