After changing flush mode from auto to commit, I now get a foreign key constraint violation when an existing entity was modified.
It looks like ValidityAuditStrategy.perform() is not flushing the session when flush mode is set to commit. Therefore the revision entity is not present in the database when ValidityAuditStrategy tries to update REVEND.
com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException
Cannot add or update a child row: a foreign key constraint fails (`pim`.`pim_feature_groups_AUD`, CONSTRAINT `FK_d82a6ca0ceda4dd5a2f2f49a41a` FOREIGN KEY (`REVEND`) REFERENCES `custom_revisions` (`id`))
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira