It seems I have identified the possible reason. In my code first I am calling child remove then parent remove.This is the most Ideal way of working the remove. But in Tomee+ it seems when transaction is commit, it is first calling parent remove and then child remove and at the same time database cascade is also trying to delete child because it is getting triggered by parent delete.
Is there any way in OpenEjb such that at commit it maintain the order of calling remove as in the code? Thanks, Bibhuti -- View this message in context: http://openejb.979440.n4.nabble.com/Optimi-sticLockException-Optimistic-locking-errors-were-detected-when-flushing-to-the-data-store-tp4660338p4660429.html Sent from the OpenEJB User mailing list archive at Nabble.com.
