commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DBCP-146) [dbcp] Invalidate "broken" connections by monitoring SQLExceptions
Date Mon, 15 Feb 2010 04:39:28 GMT

     [ https://issues.apache.org/jira/browse/DBCP-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Phil Steitz updated DBCP-146:
-----------------------------

    Fix Version/s:     (was: 1.4)
                   2.0

> [dbcp] Invalidate "broken" connections by monitoring SQLExceptions
> ------------------------------------------------------------------
>
>                 Key: DBCP-146
>                 URL: https://issues.apache.org/jira/browse/DBCP-146
>             Project: Commons Dbcp
>          Issue Type: Improvement
>    Affects Versions: 1.1
>         Environment: Operating System: All
> Platform: All
>            Reporter: Dirk Verbeeck
>            Priority: Minor
>             Fix For: 2.0
>
>         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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message