There is a bug in JDBCAppender's execute method. If there is a SQLException, the connection is not closed. The best place to close a connection/statement is in "finally". What's happening now, is I'm getting a connection leak every time an SQL exception happens.
BTW, the log also gets lost. Shouldn't the fallback handler kick in here? Regards Milind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
