[
https://issues.apache.org/jira/browse/POOL-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz updated POOL-113:
-----------------------------
Fix Version/s: (was: 1.4)
2.0
The relevant classes in the 1.4 release branch have been patched address this
issue. Leaving open for 2.0
> Inconsistent synch in InvalidEvictorLender, GenericKeyedObjectPool,
> GenericObjectPool
> -------------------------------------------------------------------------------------
>
> Key: POOL-113
> URL: https://issues.apache.org/jira/browse/POOL-113
> Project: Commons Pool
> Issue Type: Bug
> Reporter: Sebb
> Fix For: 2.0
>
> Attachments: InvalidEvictorLender.txt
>
>
> InvalidEvictorLender does not always synchronize referant field.
> Patch to follow - please check that the correct synch object is used.
> Similar problems apply to GenericKeyedObjectPool:
> Inconsistent synchronization of
> org.apache.commons.pool.impl.GenericKeyedObjectPool._testOnBorrow; locked 66%
> of time
> GenericKeyedObjectPool.java line 913
> Inconsistent synchronization of
> org.apache.commons.pool.impl.GenericKeyedObjectPool._testOnReturn; locked 66%
> of time
> GenericKeyedObjectPool.java line 1096
> And to GenericObjectPool:
> Inconsistent synchronization of
> org.apache.commons.pool.impl.GenericObjectPool._testOnBorrow; locked 66% of
> time
> GenericObjectPool.java line 915
> Inconsistent synchronization of
> org.apache.commons.pool.impl.GenericObjectPool._testOnReturn; locked 66% of
> time
> GenericObjectPool.java line 1017
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
