commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Singaravelu Suburayan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DBCP-343) RemoveAbandoned setting closes the active connection.
Date Mon, 13 Sep 2010 09:44:32 GMT

    [ https://issues.apache.org/jira/browse/DBCP-343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12908679#action_12908679
] 

Singaravelu Suburayan commented on DBCP-343:
--------------------------------------------

I got it. Thanks for the details.

Is it possible to do in this way? Is it possible to maintain the state of the connection,
say executionMode or idleMode. when the execute* method of the statement is called, the connection
object will be flaged with executionMode and once it is done with the operation it can come
back to the idleMode. the cleanup mechanism can only closes the connections which are in idleMode


> RemoveAbandoned setting closes the active connection.
> -----------------------------------------------------
>
>                 Key: DBCP-343
>                 URL: https://issues.apache.org/jira/browse/DBCP-343
>             Project: Commons Dbcp
>          Issue Type: Bug
>    Affects Versions: 1.4
>         Environment: Linux 64 bit, Ubuntu 5.*
>            Reporter: Singaravelu Suburayan
>            Priority: Blocker
>
> 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.


Mime
View raw message