actually isolationlevel SERIALIZABLE should result in what you expect to happen since it makes use of EDU.oswego.cs.dl.util.concurrent.FIFOSemaphore wrapped into an Identitylock as implementation of Sync. Thus read-locks are treated the same as write-locks and will block until the end of Transaction as long the previous lock is not owned by the same Globaltransaction.
Therefore the way your code runs depends on the behaviour of the transactionmanager being used since you start the second Transaction from the thread that is started within the boundaries of the first Transaction. To be independent of TransactionManagerImplementation-specific behaviour try starting the 2nd thread first before opening the first transaction. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3854729#3854729 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3854729 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
