commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Kranz (JIRA)" <j...@apache.org>
Subject [jira] Created: (DBCP-325) Abandoned Connection Timeout
Date Tue, 23 Feb 2010 14:56:28 GMT
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.


Mime
View raw message