DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27438>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27438 JDBCAppender doesn't release connection in case of failure ------- Additional Comments From [EMAIL PROTECTED] 2004-04-01 22:46 ------- Hi Gino, You're right that the JDBCAppender is not of production quality. This is the second problem I discovered in this class. The first was when we were using an old version of log4j which has the persistent major memory leak in the flush method and the most recent memory leak due to stale connection. This parcular problem is very subtle(which could be caused the firewall or a *database restart or crash.*) as it's very hard to pinpoint where the memory leak is occuring in. In a J2EE environment it is ill advised to use file based logging destination as it contravene the EJB specification rule. This is where JDBCAppender or JMSType destination could be use. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
