You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Patrick Kranz (JIRA)" <ji...@apache.org> on 2010/02/23 15:56:28 UTC

[jira] Created: (DBCP-325) Abandoned Connection Timeout

Abandoned Connection Timeout
----------------------------

                 Key: DBCP-325
                 URL: https://issues.apache.org/jira/browse/DBCP-325
             Project: Commons Dbcp
          Issue Type: New Feature
            Reporter: Patrick Kranz
            Priority: Trivial


It would be nice to have a timeout that specifies how long a connection, on which close() has been called, should be held in the pool, even if this connection exceeds the maxIdle limit. This would make it possible to say something like "I know this is one more idle connection than I configured but keep it around for just a few more seconds in case we have a second peak so we don´t need to construct the connection again".

If this has a chance of getting into the pool, I would try to provide a patch that implements this so that, in best case, you only would have to do a code review.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (DBCP-325) Allow idle connection count to exceed maxIdle for configurable time period

Posted by "Phil Steitz (JIRA)" <ji...@apache.org>.

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

Phil Steitz updated DBCP-325:
-----------------------------

    Summary: Allow idle connection count to exceed maxIdle for configurable time period  (was: Abandoned Connection Timeout)

> Allow idle connection count to exceed maxIdle for configurable time period
> --------------------------------------------------------------------------
>
>                 Key: DBCP-325
>                 URL: https://issues.apache.org/jira/browse/DBCP-325
>             Project: Commons Dbcp
>          Issue Type: New Feature
>            Reporter: Patrick Kranz
>            Priority: Trivial
>
> It would be nice to have a timeout that specifies how long a connection, on which close() has been called, should be held in the pool, even if this connection exceeds the maxIdle limit. This would make it possible to say something like "I know this is one more idle connection than I configured but keep it around for just a few more seconds in case we have a second peak so we don´t need to construct the connection again".
> If this has a chance of getting into the pool, I would try to provide a patch that implements this so that, in best case, you only would have to do a code review.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.