[
https://issues.apache.org/jira/browse/POOL-125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700062#action_12700062
]
Mark Thomas commented on POOL-125:
----------------------------------
Take a look at DBCP-44. There is at least one use case described in that bug
that, despite correct usage by the user, can result in a deadlock.
As an aside, I have a patch for this for GOP and am in the process of porting
similar changes to GKOP.
> Insufficient control over concurrent access to pooled objects by Evictor,
> client threads
> ----------------------------------------------------------------------------------------
>
> Key: POOL-125
> URL: https://issues.apache.org/jira/browse/POOL-125
> Project: Commons Pool
> Issue Type: Bug
> Affects Versions: 1.2, 1.4
> Reporter: Phil Steitz
> Fix For: 1.5
>
>
> In pool 1.2, 1.4, borrowObject, returnObject, invalidateObject are not fully
> synchronized. This creates the potential for race conditions vis a vis the
> Evictor and/or client object lock contention. Factory methods on pooled
> objects should not be allowed to be invoked concurrently by client threads
> and the Evictor.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
