[jira] Commented: (POOL-87) Commons-Pool does not always calling activateObject on newly created Objects

[ http://issues.apache.org/jira/browse/POOL-87?page=comments#action_12441771 ] Bernie McGourty commented on POOL-87: - OK, I guess I misunderstood. I've modified my PoolableObjectFactory to call activateObject after constructing the object in

[jira] Commented: (POOL-87) Commons-Pool does not always calling activateObject on newly created Objects

[ http://issues.apache.org/jira/browse/POOL-87?page=comments#action_12441750 ] Sandy McArthur commented on POOL-87: Poolable Objects created by makeObject() are considered to be an active state so they do not need to be activated again. I'll

[jira] Commented: (POOL-87) Commons-Pool does not always calling activateObject on newly created Objects

[ http://issues.apache.org/jira/browse/POOL-87?page=comments#action_12441638 ] Sandy McArthur commented on POOL-87: If poolable objects are being made simply to ensure a minIdle threshold, then they would go directly into the idle object poo