0 Replies Latest reply on Aug 8, 2016 9:44 PM by Stephan Beltran

    Hibernate Envers and JPA Transactions - Unable to create revision because of non-active transaction

    Stephan Beltran Newbie

      I've been trying to wrap my head around this issue all day.

       

      Currently our project has setup JPATransactionManager to take care of our various session transactions with the use of @Transactional on all services that take care of persistence and deletions (DAO usage).

       

      Changing over from Hibernate 3 to 5, we wanted to remove our use of a custom audit interceptor and move onto using Hibernate Envers. I have annotated all my classes properly and have the tables being created, but once it actually gets to a point of insertion, the listener throws an error in which it can't find the current transaction given by JPA:

       

      org.hibernate.envers.exception.AuditException: Unable to create revision because of non-active transaction

          at org.hibernate.envers.event.spi.BaseEnversEventListener.checkIfTransactionInProgress(BaseEnversEventListener.java:132)

          at org.hibernate.envers.event.spi.EnversPostInsertEventListenerImpl.onPostInsert(EnversPostInsertEventListenerImpl.java:34)

          at org.hibernate.action.internal.EntityIdentityInsertAction.postInsert(EntityIdentityInsertAction.java:156)

          at org.hibernate.action.internal.EntityIdentityInsertAction.execute(EntityIdentityInsertAction.java:102)

          at org.hibernate.engine.spi.ActionQueue.execute(ActionQueue.java:597)

          at org.hibernate.engine.spi.ActionQueue.addResolvedEntityInsertAction(ActionQueue.java:232)

          at org.hibernate.engine.spi.ActionQueue.addInsertAction(ActionQueue.java:213)

          at org.hibernate.engine.spi.ActionQueue.addAction(ActionQueue.java:256)

          at org.hibernate.event.internal.AbstractSaveEventListener.addInsertAction(AbstractSaveEventListener.java:318)

          at org.hibernate.event.internal.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:275)

          at org.hibernate.event.internal.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:182)

          at org.hibernate.event.internal.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:113)

          at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:192)

          at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:177)

          at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:97)

          at org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:73)

          at org.hibernate.internal.SessionImpl.fireSaveOrUpdate(SessionImpl.java:651)

          at org.hibernate.internal.SessionImpl.saveOrUpdate(SessionImpl.java:643)

          at org.hibernate.internal.SessionImpl.saveOrUpdate(SessionImpl.java:638)

       

       

       

      Looking inside the code, it seems that it's basing the transaction status off it's default value of INACTIVE meaning that it's not hooking into the transaction properly. I know that Hibernate Envers also automatically pushes the listeners into hibernate with recent versions so I don't know if this may also be a source of the issue.

       

      I know that its been documented to work with HibernateTransactionManager but we wish to step away from using that in favor of hooking up our transactions and sessions solely via Spring making things easier so it may also be the need of finding an alternative to envers. Does anyone have any advice or solutions to this problem? Or also hit this issue?