commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <>
Subject [jira] Updated: (DBCP-156) [dbcp] Specifying the maximum lifetime of a connection
Date Mon, 10 Jul 2006 05:02:32 GMT
     [ ]

Phil Steitz updated DBCP-156:

    Bugzilla Id:   (was: 28211)
    Fix Version: 1.3

> [dbcp] Specifying the maximum lifetime of a connection
> ------------------------------------------------------
>          Key: DBCP-156
>          URL:
>      Project: Commons Dbcp
>         Type: Improvement

>     Versions: 1.1 Final
>  Environment: Operating System: All
> Platform: All
>     Reporter: Juergen Hoeller
>     Priority: Minor
>      Fix For: 1.3

> It would be excellent if BasicDataSource had a "maxLifetime" property, for 
> specifying the maximum lifetime of a connection in the pool, no matter how long 
> it's been active or idle, and no matter whether it still seems to be alive. 
> Commons DBCP does not support this yet; it just offers various connection 
> validation means, which is not the same.
> This is particularly relevant for MySQL Connector/J 3.0.x which tries to apply 
> some weird automatic recovery when a MySQL connection has timed out, resulting 
> in all sorts of issues. The best way to deal with this is to set the maximum 
> lifetime of a connection to 4 hours or the like: If it's older, simply kill it, 
> even if it's still alive at that point of time.
> Note that Proxool ( does have such a property, 
> namely "maximum-connection-lifetime". Resin's connection pool has a similar 
> property named "max-pool-time" (
> config.xtp). I tend to prefer Commons DBCP, but the lack of such a property 
> forces me to look for alternative pools.
> Juergen

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message