Hi everybody, I started using Log4j last week and find it a really great product. We will be using Log4J in a performance critical application. As appenders we will use the FileAppender, SocketAppender and JDBCAppender. After some tests however, I noticed that the performance of log4j is severly degraded when there is a blockage on the Database level.
The execution time of the program was more than 76 times higher. When I stop the database (to simulate a crash) the execution time is even much worse (more than 2790 times higher) which is unacceptable off course. Does anyone encountered the same problem, or knows how to deal with it? We could rewrite the JDBCAppender but prefer not to, due to time limitations. Thanks in advance for your comments and suggestions Best regards Jeroen Frissaer -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
