You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2005/11/02 22:49:10 UTC

DO NOT REPLY [Bug 37337] New: - GenericObjectPool WHEN_EXHAUSTED_BLOCK behvior could wait almost twice as long as desired

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37337>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37337

           Summary: GenericObjectPool WHEN_EXHAUSTED_BLOCK behvior could
                    wait almost twice as long as desired
           Product: Commons
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Pool
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: Sandy@McArthur.org


Very minor bug: On lines 797 of GenericObjectPool and lines 809 of GenericKeyedObjectPool the code is 
such that if the pool is exhausted and the thread waits and is notified shortly before _maxWait time has 
elapsed then then the thread may end up waiting for another period of _maxWait. Combined with the 
previous wait the thread could have actually waited almost twice the desired time. The correct behavior 
would be to do the math and wait a lesser amount adjusted for the previous wait interval.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org