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-03-29 01:11 ------- In environments where corporate firewall exists between the deamon process that uses JDBCAppender and the database, these cached JDBC connections are invalidated by the firewall as a result of being inactive beyond a certain period, .eg 30 minutes. The manner in which the JDBCAppender has been implemented will never recover from this failed condition. What's worst is it actually introdcued memory leak. A study of the flush method reveals that logger events are never removed whenever an exception occurs. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
