As I understand it, SimpleReadWriteEJBLock obtains a shared read lock on the entity until someone request promotion to a write lock, at which point other readers are rolled back.
I am wondering how you achieve this with Oracle, which does not support read locks. Is it the case that you do not use the database locking features (i.e. you do not use JDBC isolation levels) but instead you use synchronized locks within JBoss? So you are not dependent on the database features? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861894#3861894 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861894 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
