Are you setting the 'openjpa.RuntimeUnenhancedClasses' property to 'supported', if so don't?
You could also try using @TransactionManagement(TransactionManagementType.BEAN) and manage your own transaction. @Resource private UserTransaction transaction; ... transaction.begin(); ... delete ... transaction.commit(); -- View this message in context: http://openejb.979440.n4.nabble.com/Optimi-sticLockException-Optimistic-locking-errors-were-detected-when-flushing-to-the-data-store-tp4660338p4660352.html Sent from the OpenEJB User mailing list archive at Nabble.com.
