[ http://issues.apache.org/jira/browse/POOL-75?page=all ] Sandy McArthur closed POOL-75: ------------------------------
Resolution: Later Untill Pool can use the util.concurrent package this will have to wait. > [pool] GenericObjectPool not FIFO with respect to borrowing threads > ------------------------------------------------------------------- > > Key: POOL-75 > URL: http://issues.apache.org/jira/browse/POOL-75 > Project: Commons Pool > Type: Improvement > Versions: Nightly Builds > Environment: Operating System: All > Platform: All > Reporter: Gordon Mohr > Priority: Minor > > GenericObjectPool has recently been made FIFO with respect to the managed pool > objects -- however, it is still not FIFO with respect to threads requesting > those objects. Specifically, because standard non-fair Java synchronization > monitors are used, later threads may barge ahead of earlier threads that are > already waiting for a pool object to become available. At its extreme, some > threads can cycle objects through the pool many times while others wait > interminable. > Not every application needs FIFO fairness with respect to threads, and such > fairness implies an overhead, so it need not be the default behavior, but it > would be a valuable option where many threads are sharing a smaller number of > pool objects. > I can submit a FairGenericObjectPool which achieves thread-fairness; it only > requires small changes to GenericObjectPool which allow some subclass > overriding. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]