posted 14 years ago
I found the reason for this exception, the table which I was trying to update did not have any constraints defined on it, not even primary key. Accidently, the same data scripts had been run twice thus returning two rows for update.
I still dont know why Open Jpa should throw an OptimisticLockException, but that is what the issue was.
Thanks anyway!