[
https://issues.apache.org/jira/browse/POOL-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710284#action_12710284
]
Tom commented on POOL-92:
-------------------------
My my, back in 2006 I see. What I remember so off the top off my head is
that when you have a limited set of entities to be pooled, that the
current implemention goes into a endless loop because it is not able to
allocate one. AFAIK there was severe reluctance to accept that the pool
was being used in such a scenario, and there was -in my opinion- no
interest in any fixes. So I ended up implementing my own version which
is now in production for, well, 3 years. :-)
As I remember, in my implementation I chose to use an abstract base
class for the pooling algorithm and only override the main "who's next"
logic per implementation. This made the code fairly clean. As said then,
I'm willing to send my code and then you can see what you want to do
with it.
Tom
> the 1.3 implementation has a problem with finite sized pools, this
> improvement contains an alternate implementation
> -------------------------------------------------------------------------------------------------------------------
>
> Key: POOL-92
> URL: https://issues.apache.org/jira/browse/POOL-92
> Project: Commons Pool
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Tom
> Fix For: 3.0
>
> Attachments: pool.zip
>
>
> The implementation is not yet 100% complete. For example it doesn't have an
> eviction thread, but the core is fully functional.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
