[
https://issues.apache.org/jira/browse/POOL-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16667622#comment-16667622
]
Paul Pazderski commented on POOL-327:
-------------------------------------
Yes, since both issues address the same problem and the fix for POOL-356 is in
essence equal to 327-maxIdle0-alternativ.patch I'm quite sure it will solve
this.
Apart from that, there is still my unit test to be sure.
> GKOP: returnObject does not unblock threads waiting in borrowObject if
> maxIdle=0
> --------------------------------------------------------------------------------
>
> Key: POOL-327
> URL: https://issues.apache.org/jira/browse/POOL-327
> Project: Commons Pool
> Issue Type: Bug
> Affects Versions: 2.4.2
> Reporter: Paul Pazderski
> Assignee: Mark Struberg
> Priority: Minor
> Fix For: 2.6.1
>
> Attachments: 327-maxIdle0-alternativ.patch, 327-maxIdle0-test.patch,
> 327-maxIdle0.patch
>
>
> If idle objects are disabled by maxIdle=0 a thread blocked in borrowObject is
> not notified if another thread returns an object.
> Attached is a unit test (327-maxIdle0-test.patch) that demonstrates the
> issue. I tried a similar test on GenericKeyedObjectPool as well which not
> seems to be affected by this issue.
> I also attached two possible solutions for this issue.
> The first (327-maxIdle0.patch) just notifies a potentially waiting thread in
> the affected returnObject code branch. (similar to POOL-240)
> The second (327-maxIdle0-alternativ.patch) checks for waiting threads every
> time an object get destroyed. But this may introduce undesired behavior in
> other functions. (like clear or evict)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
