[
https://issues.apache.org/jira/browse/POOL-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Thomas resolved POOL-263.
------------------------------
Resolution: Fixed
Fix Version/s: 2.3
This issue is fixed but a reliable test case isn't possible without polluting
the GOP and GKOP code which I would rather not do.
> GenericObjectPool close and returnObject is not synchronized
> ------------------------------------------------------------
>
> Key: POOL-263
> URL: https://issues.apache.org/jira/browse/POOL-263
> Project: Commons Pool
> Issue Type: Bug
> Affects Versions: 2.2
> Environment: ALL
> Reporter: yangxuesong
> Fix For: 2.3
>
>
> the javadoc on GenericObjectPool#close() says:
> "Closes the pool. Once the pool is closed, borrowObject() will fail with
> IllegalStateException, but returnObject(Object) and invalidateObject(Object)
> will continue to work, with returned objects destroyed on return.
> Destroys idle instances in the pool by invoking clear()."
> Thread1: pool.close()
> Thread2: pool.returnObject()
> since close and returnObject is not synchronized, there is a small chance
> that an returned object is not destoryed after the pool is closed
--
This message was sent by Atlassian JIRA
(v6.2#6252)
