I have a problem with the way JBoss handles concurrent access to entity
beans from different transactions. The behaviour is to lock the thread
accessing the bean from a second transaction until the first transaction
commits. What we were hoping for was that it would throw an exception and
allow the second transaction to be rolled back.

Is there some way to configure this behavioiur in JBoss or is it simply the
way JBoss interprets the specification.

Tim Kemp 

_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to