[jira] Updated: (POOL-3) [pool] GenericObjectPool WHEN_EXHAUSTED_BLOCK behvior could wait almost twice as long as desired

["Henri Yandell (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/POOL-3?page=all ]

Henri Yandell updated POOL-3:
-----------------------------

    Bugzilla Id:   (was: 37337)
    Fix Version: 1.3

> [pool] GenericObjectPool WHEN_EXHAUSTED_BLOCK behvior could wait almost twice as long as desired
> ------------------------------------------------------------------------------------------------
>
>          Key: POOL-3
>          URL: http://issues.apache.org/jira/browse/POOL-3
>      Project: Commons Pool
>         Type: Bug

>  Environment: Operating System: All
> Platform: All
>     Reporter: Sandy McArthur (from Bugzilla import)
>     Priority: Minor
>      Fix For: 1.3

>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


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