commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phil Steitz (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (DBCP-343) RemoveAbandoned setting closes the active connection.
Date Wed, 25 Feb 2015 00:26:05 GMT

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

Phil Steitz reopened DBCP-343:
------------------------------

Should be resolved, but not closed (pending 1.4.1 release)

> 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.3, 1.4
>         Environment: Linux 64 bit, Ubuntu 5.*
>            Reporter: Singaravelu Suburayan
>            Priority: Blocker
>             Fix For: 1.3.1, 1.4.1
>
>         Attachments: removeAbandoned.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message