[
https://issues.apache.org/jira/browse/DBCP-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908727#action_12908727
]
Phil Steitz commented on DBCP-343:
----------------------------------
Patches welcome on javadoc. To be clear, it is not strictly speaking the age
of the Delegating statement that counts, it when it was last used. My comment
above may have been misleading. Have a look at
DelegatingStatement,executeQuery() for example. If you can confirm actual JDBC
operations that do not update lastUsed, then we should view this as a bug.
> RemoveAbandoned setting closes the active connection.
> -----------------------------------------------------
>
> Key: DBCP-343
> URL: https://issues.apache.org/jira/browse/DBCP-343
> Project: Commons Dbcp
> Issue Type: Improvement
> Affects Versions: 1.4
> Environment: Linux 64 bit, Ubuntu 5.*
> Reporter: Singaravelu Suburayan
> Priority: Blocker
> Fix For: 2.0
>
>
> The documentation says, RemoveAbandoned connection setting will remove only
> the connections that are idle for the configured timeout. But I see it is
> closing the connections that are active.
> The logic in DBCP implementatoin shows that it calculate the idle time from
> the time of the connection is created, irrespective of the connection is
> used. So it just close the connection in removeAbandonedTimeout.
> In my code, I'm reusing the connection for more DB statements to do intensive
> db operations, which hold the connection for more than 5 minutes . The
> connection will never be idle for more than a few seconds.
> My setting of removeabandonedTimeout = 300 brutally closes the connection in
> 5 minutes, without checking if the connection is in use or not.
> I assume it should involve the activity of the statement object also to do
> the idle time calculation.
> thanks,
> Sing
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
