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 33264] New: - GenericObjectPool is a LIFO, not a FIFO implementation
Date Thu, 27 Jan 2005 07:48:19 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=33264>.
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=33264

           Summary: GenericObjectPool is a LIFO, not a FIFO implementation
           Product: Commons
           Version: 1.2 Final
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Pool
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: thomas@schuerger.com


Hi,

the GenericObjectPool implementation is (like the StackedObjectPool) a LIFO, not
a FIFO implementation  as stated here:
http://jakarta.apache.org/commons/pool/guide/index.html).

When borrowObject() is called, the first available object is extracted from the
pool using removeFirst(). When returnObject(obj) is called, the object is
returned to the pool using addFirst(). I would expect that addLast() is used if
this is supposed to be a FIFO implementation.

But perhaps the developers guide is wrong, not the implementation.

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