Uploaded image for project: 'Commons DBCP'
  1. Commons DBCP
  2. DBCP-343

RemoveAbandoned setting closes the active connection.

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.3, 1.4
    • Fix Version/s: 1.3.1, 1.4.1
    • Labels:
      None
    • Environment:

      Linux 64 bit, Ubuntu 5.*

      Description

      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

        Attachments

        1. removeAbandoned.patch
          25 kB
          Phil Steitz

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              singaravelu Singaravelu Suburayan
            • Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: