[
https://issues.apache.org/jira/browse/POOL-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Thomas resolved POOL-119.
------------------------------
Resolution: Won't Fix
Since there appears to be no interest in providing a patch for what appears to
me to be a use case of limited interest, I am resolving this as "Won't Fix".,
Regarding the serial creation for ensureMinIdle(), this is happening on a
background thread so should not block normal usage. Object creation speed isn't
an issue here since if there aren't enough idle objects, borrow object will
create them as required the evictor won't have any idle objects to remove so
the fact that it is spending some time creating objects and not evicting them
is not an issue. The idle object tests also won't be happening but under this
scenario I don;t image there will be that many idle objects anyway.
> GenericObjectPool: Provide option to create new objects serial
> --------------------------------------------------------------
>
> Key: POOL-119
> URL: https://issues.apache.org/jira/browse/POOL-119
> Project: Commons Pool
> Issue Type: New Feature
> Affects Versions: 1.4
> Reporter: Christoph Kutzinski
> Fix For: 2.0
>
> Attachments: patch.txt, patch2.txt
>
>
> As discussed on the Commons-Dev mailing list:
> In certain scenarios it is desirable to serialize creation of new objects, if
> the pool needs to grow. This has 2 main advantages:
> - help keeping load away from the engine creating the objects (e.g. the
> database server) during high load situations
> - avoid unnecessary object creation if objects where returned to pool while
> multiple 'new' objects are requested from the pool
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
