OConcurrentModificationException hidden [moved]

[lvca]

This is Issue 277 moved from a Google Code project.
Added by 2011-03-23T19:32:15.000Z by sylvain....@gmail.com.
Please review that bug for more context and additional comments, but update this bug.
Closed (Fixed).

Original labels: Type-Defect, Priority-Medium, v1.0rc1

Original description

If an OConcurrentModificationException is thrown on a save() call while the optimistic transaction is in TXSTATUS.COMMITTING, this exception is catched and wrapped in 3 Orient internal methods. 

In these cases, we can't detect easily the OConcurrentModificationException in order to re-execute the code.

Here is a small patch that correct the problem.