We got again the issue with the objects staying modified after the synchronous EDS commit throwing an exception. We were able to reproduce it several times. The transaction had several inserts and updates. The updated objects were modified after the rollback, no notification was sent to containers. The data inconsistency destroyed the application business logic completely.
PS: The application code DOES NOT modify the objects read from the embeded space. We are always using object copy to set the new values. There is even a warning printed if someone tries to do it - custom application object lifecycle.
com.gigaspaces.test.support.cabank.case6469.CommitFailExceptionTest /./qaSpace?schema=persistent&cluster_schema=partitioned-sync2backup&total_members=1,1 embedded