[ http://issues.apache.org/jira/browse/DBCP-146?page=all ]
Phil Steitz updated DBCP-146: ----------------------------- Bugzilla Id: (was: 26759) Fix Version: 1.3 > [dbcp] Invalidate "broken" connections by monitoring SQLExceptions > ------------------------------------------------------------------ > > Key: DBCP-146 > URL: http://issues.apache.org/jira/browse/DBCP-146 > Project: Commons Dbcp > Type: Improvement > Versions: 1.1 Final > Environment: Operating System: All > Platform: All > Reporter: Dirk Verbeeck > Priority: Minor > Fix For: 1.3 > Attachments: brokenConn-patch.txt > > A PoolableConnection can know when it is "broken". (When a fatal SQLException > is > thrown.) A SQLException is considered fatal when it includes an error code > from > a configurable list of broken connection indicators. > The attached patch is a partial implementation for review > (not all Delegating* methods are covered) > Summary: > Add a list of indicators that (when found in an SQLException) mark a > Connection > as "broken". Broken Connections will be destroyed and not returned to the > pool. > if (!isBroken()) { > _pool.returnObject(this); > } else { > _pool.invalidateObject(this); > } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]