commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 39314] New: - [pool] Pool grows beyond MaxActive with WHEN_EXHAUSTED_BLOCK
Date Fri, 14 Apr 2006 15:49:31 GMT
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=39314>.
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=39314

           Summary: [pool] Pool grows beyond MaxActive with
                    WHEN_EXHAUSTED_BLOCK
           Product: Commons
           Version: 1.3 Final
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: critical
          Priority: P1
         Component: Pool
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: juergen@jwi.de


As I understand, with WHEN_EXHAUSTED_BLOCK the GenericObjectPool may not grow
above maxActive, i.e. the factory's makeObject() cannot be called more than
maxActive times.

But in the attached example code makeObject() gets called more than maxActive times.

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


Mime
View raw message