In our production system, we log to the file system and to the DB. In the event of a catastrophic failure in olmApp the same error gets logged over and over again to not only the server.log file, but also to the db. To prevent us from filling the disk on either the app server or the db server, we need to put some throttling in place.
Does log4j have the ability to do this? It was not obvious to me how to do this after looking through the FAQ and the documentation. For the file system we use org.jboss.logging.appender.DailyRollingFileAppender and for the DB we use our own DataSourceAppender which extends org.apache.log4j.jdbc.JDBCAppender. We are running on JBoss 4.0.4.GA. Thanks, Frank --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
