Ben, Bela; Wondering if you can explain why ReadWriteLockWithUpgrade.upgradeLockAttempt() does not allow more than 1 concurrent reader to upgrade their lock?
Although there are inherent inefficiencies if you have many readers competing for a lock upgrade, I can't see an inherent problem with the scenario. In my case, I do have situations where multiple threads are trying to add different children to the same node on a cache with REPEATABLE_READ as the isolation level. Any thoughts on this? Brian. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883911#3883911 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3883911 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
