Possible Envers Validity Audit Strategy Bug - Can Anyone Confirm?

Question

We have a Seam 2 application running on JBoss AS 7. In order to speed up access to historical revisions of entities, we switched to the Envers Validity Audit Strategy. Everything seemed ok, but then saving one particular type of entity would cause a

org.hibernate.AssertionFailure: possible nonthreadsafe access to session

error. Turning off the Validity Audit Strategy fixed the problem.

Has anyone had any success with the Validity Audit Strategy (the docs do say that it is experimental)?

I should point out we are using Hibernate 3.6.8.Final.

Answer 1

I think the issue is to do with the FlushMode. See https://hibernate.onjira.com/browse/HHH-7329?focusedCommentId=46833#comment-46833 for an explanation of how to fix this issue.