Atomikos Forum

Hi guys,
We've been using Atomikos TransactionEssentials successfully for a couple of months, and we now need to use Hibernate Envers to audit one of our tables...
The problem is that it seems the Envers listener never gets called...
Did somebody managed to get Atomikos TransactionEssentials and Hibernate Envers to work together?

Thank you,
Phil

We're using:
 - Atomikos Essentials 3.6.5
 - Hibernate 3.5.1-Final
 - Hibernate Envers 3.5.1-Final
 - Spring 3.0.0.RELEASE

We fixed our problem by adding:
<prop key="hibernate.current_session_context_class">jta</prop>
to the hibernate properties in our session factory bean.

We're not sure why using Envers would make this property required. Or maybe the problem we had didn't really appear because we started using Envers.

We tried to add this property because we saw it in the Spring Integration documentation:
http://www.atomikos.com/Documentation/SpringIntegration#Spring_s_HibernateTemplate

But we also looked at the Hibernate Integration documentation:
http://www.atomikos.com/Documentation/HibernateIntegration#With_Spring

and this property is not defined in this page.

Is it an error?
Should the "hibernate.current_session_context_class" property always be set to "jta" when using Atomikos?

Thanks,
Phil

Hi,

Could you take a look at the following Hibernate issue ( http://opensource.atlassian.com/projects/hibernate/browse/HHH-5315 ).

Atomikos + Hibernate Envers + Spring worked OK for us, but since 3.5.1 we're facing this issue. I'm still not sure if this is a Hibernate or an Atomikos issue, since I can only reproduce this with Atomikos as the JTA transaction manager.

From the Hibernate JIRA description I can only assume that this is a problem in the flushing of Hibernate's: this should be done on beforeCompletion, and my first impression is that it does this on afterCompletion (which is wrong)?

Again, this is just a first impression and I have no further evidence to justify this.