sorry - i haven't answered earlier ... no - flush is NOT committing your transaction ! Your transaction is finished after you are leaving the SLSB --> when leaving the SLSB the container is running through several "intercepors" and is finishing the transaction - in other words it commits the changed data into the database !!! Before that - no other call can see the modified data (except you change the default behaviour of the container which is usually "read-commited") !
So if another thread of your frontend starts a second SLSB trying to modify the same entity it will still see the OLD data as long as the other call is not committed ! Thats why I asked you to "synchronize" your calls with the introduction of "version" which uses optimistic locking !!! You should get an exception in one of both transactions but not yours ;-) hope I could help you ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994006#3994006 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994006 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
