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

Test for idle time exceeded in borrowObject

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Won't Fix
    • 1.3
    • None
    • None

    Description

      For GenericObjectPool, the evictor thread performs a calculation to determine if an idle object as "expired." If it has, the object is destroyed.

      Would like borrowObject to perform the same test and destroy behavior.

      I explored using the testOnBorrow facility but the time that the object went idle is not available. Only the pool has access to the ObjectTimestampPair object that is used to record the time that the object was placed in the pool. I explored placing a timestamp in the pooled object and can do that but it would seem better if the pool managed that test itself.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            reamon Rob Eamon
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment