deepak created POOL-232:
---------------------------
Summary: GOP: borrowObject() & returnObject() are still not FIFO
Key: POOL-232
URL: https://issues.apache.org/jira/browse/POOL-232
Project: Commons Pool
Issue Type: Bug
Affects Versions: 1.6
Reporter: deepak
Latest Pool API (1.6) is still not implemented the fairness policy, because of
the usage of the synchronized construct in the two important borrowObject() &
returnObject() APIs
If you have very high no. of clients threads, trying to invoke either
borrowObject() & returnObject() APIs, then their order will not be respected
because synchronized keyword doesn't guarantee the fairness. ReentrantLock
could be used in both the APIs in order to have the fairness policy implemented.
Though in the past, someone raised the exact same issue (POOL-75), but don't
really understand that how it is fixed when issue seems to be still present.
I am from telecom industry, and I use this library in the reall time call flow,
so for me fairness is very important.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
