Uploaded image for project: 'Commons Pool'
  1. Commons Pool
  2. POOL-125

Insufficient control over concurrent access to pooled objects by Evictor, client threads

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.2, 1.4
    • 1.5
    • None

    Description

      In pool 1.2, 1.4, borrowObject, returnObject, invalidateObject are not fully synchronized. This creates the potential for race conditions vis a vis the Evictor and/or client object lock contention. Factory methods on pooled objects should not be allowed to be invoked concurrently by client threads and the Evictor.

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. DBCP-44 [dbcp] Evictor thread in GenericObjectPool has potential for deadlock

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              psteitz Phil Steitz
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: