[ http://issues.apache.org/jira/browse/POOL-93?page=comments#action_12452547 ] Holger Hoffstätte commented on POOL-93: ---------------------------------------
Thought about that too; AFAIK volatile is not really broken any more, at least not for volatile reads & synchronized writes as done in the backport (see e.g. Atomic*). Also found this: http://www.cs.umd.edu/~pugh/java/memoryModel/archive/1888.html Got to draw the line somewhere :-) Maybe use the getter for 1.3.x and then assume a working volatile for 2.0? That way we can also start relaxing other areas where possible, step by step. > Reduce contention by making borrow & return more independent from each other > ---------------------------------------------------------------------------- > > Key: POOL-93 > URL: http://issues.apache.org/jira/browse/POOL-93 > Project: Commons Pool > Issue Type: Improvement > Affects Versions: Nightly Builds > Reporter: Holger Hoffstätte > Attachments: GKOP-relaxedSyncOnReturn.patch, > relaxedReturnObjectBenchmark.txt > > > Currently borrow & return are completely blocked from each other, while at > least the factory-based validation & destruction can be handled > independently. A few simple changes narrow the synchronization blocks yet > retain overall correctness. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
