This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I am using log4j 1.2.14 in my application for logging activity. I have configured JDBC appender in log4j.xml for MSSQL server table logging. In case of handling the database down scenario I have configured FallBackErrorHandler to log in to a temporary flat file.
There is a scenario where in the JDBCAppender goes down and FallBackErrorHandler comes in to picture due to database down case, from that point the FallBackErrorHandler takes responsibility of logging.
My requirement is to invoke the JDBCAppender as soon as the Database is up and running, but that's not the case as of now, even when the database is up the logging activity is carried out by the FallBackErrorHandler.
Is there any configuration what I can make in the log4j.xml ,are any other customization in the code, so that the logging is reverted back to the JDBCAppender as soon as the database is up and running.