Thursday, August 2, 2001 07:38 AM
This is due to your isolation level. The Entity bean which is used as well as your session bean should have TRANSACTION_SERIALIZABLE isolation level. If it is not possible (due to applicative or database limitation), catch the former exception and perform some retries. You should also catch TransactionRolledBackException. These two exceptions occure when several accesses to the same ressources are performed. The first access lock the ressource and the second one cannot do anything so it returns an exception.