[ http://issues.apache.org/jira/browse/POOL-91?page=comments#action_12458935 ] Sandy McArthur commented on POOL-91: ------------------------------------
Ben, a pool can pool any "Poolable Object". That could be a Thread or just about any other reusable object. There is a difference between a Pool of pooled Threads and Threads that are part of the Pool but not the pooled objects themselves. The PoolableObjectFactory is sufficient to manage the former but Executor needs a policy because it is the latter. I'm all for moving away from forcing the client code to deal with exceptions but sometimes exceptions make sense. The Pool road map explains what I'm trying to do about that: http://wiki.apache.org/jakarta-commons/PoolRoadMap > StackObjectPool.borrowObject infinate loop when makeObject returns null > ----------------------------------------------------------------------- > > Key: POOL-91 > URL: http://issues.apache.org/jira/browse/POOL-91 > Project: Commons Pool > Issue Type: Bug > Reporter: Sandy McArthur > Assigned To: Sandy McArthur > Attachments: sample-borrow-fail-pool-policy.tar.bz2 > > > StackObjectPool.borrowObject has a infinate loop when makeObject returns null. -- 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]
