It's not a secret anymore!
The moose likes Other Open Source Projects and the fly likes log4j JDBCAppender problem Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Other Open Source Projects
Bookmark "log4j JDBCAppender problem" Watch "log4j JDBCAppender problem" New topic

log4j JDBCAppender problem

Jiafan Zhou
Ranch Hand

Joined: Sep 28, 2005
Posts: 192

I know that Log4j has a File appender called *RollingFileAppender* which basically have a maximum file size configured in Each time the file size is reached, then log4j will log all the output to another file.

However, what about the *JDBCAppender*? If the maximum database table size(maybe? this is the part which I don't understand... Can we have such a maximum threshold to control the JDBCAppender?) is reached, how does the JDBCAppender deal with such a case?

Does it simply disallow any events being logged?
Or does it create another table?
Or does it do other fancy jobs(like low/high water mark?)?

Ideally we need this control because we don't want to end up with a super large table, right?


I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link:
subject: log4j JDBCAppender problem
It's not a secret anymore!