org.hibernate.HibernateException: The chosen transaction strategy requires access to the JTA TransactionManager

While setting up a simple web app on JBoss 5 using container manager transaction I run into following exception

Caused by: org.hibernate.HibernateException: The chosen transaction strategy requires access to the JTA TransactionManager
	at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:361)
	at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1327)

Well after some research I figured out that the cause of this were two simple configuration options in persistence.xml

First we need to make sure we are using JTA as transaction-type (by default)

  <persistence-unit name="PU_NScaffold" transaction-type="JTA">

Second make sure we have following line under properties node

  <property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup"/>

Thats it, I hope this helps someone.

20 thoughts on “org.hibernate.HibernateException: The chosen transaction strategy requires access to the JTA TransactionManager”

essnet said on February 26, 2010 at 7:41 am:

I used this tip with GlassFish v3 bundle with Netbeans and changed hibernate.transaction.manager_lookup_class value to org.hibernate.transaction.SunONETransactionManagerLookup. Problem solved! Thanks!
azzuwan said on March 13, 2010 at 11:11 am:

Thanks Greg, it works for me too
Greg said on March 17, 2010 at 9:23 pm:

I’m happy that this is useful to some people.
Leandro Bortolotto said on May 22, 2010 at 7:18 pm:

Thanks Greg and essnet, it works on glassfish v3 for me too.
Robert Moore said on May 31, 2010 at 2:46 pm:

Thanks also (on glassfish v3). I’m doing the tutorial for Wicket+JPA but now have another Hibernate problem: The CustomerJpaController.getCustomerCount() causes an exception—
java.lang.AbstractMethodError:
org.hibernate.ejb.EntityManagerImpl.getCriteriaBuilder()Ljavax/persistence/criteria/CriteriaBuilder;
Strangely enough, my first build used EclipseLink and encountered the same problem (so I rebuilt with Hibernate)
Running with JDk1.5, NB 6.8, and glassfish V3. Will provide glassfish log if needed.
Any thoughts?
Vasko Gjurovski said on July 21, 2010 at 12:05 pm:

Robert, I have the same problem. Did you manage to find a solution for it?
Zabin said on August 18, 2010 at 5:58 am:

Thanks Greg…. It helped a lottttttttttttttt
Vitorino said on October 16, 2010 at 6:51 pm:

Man, thanks a lot! You saved me from a big headache! I really really appreciate it! Kudos for your post!
Ingvar Larsson said on October 19, 2010 at 12:28 am:

Well, I also want to say thanks!!! Very very helpful!!
Aksel said on February 23, 2011 at 6:20 am:

Thanks!
This saved my day!
Im deploying on JBoss 6.0.0 Final
Greg said on February 23, 2011 at 10:43 am:

Happy to hear that.
corota said on April 24, 2011 at 6:05 pm:

Thank you for your help!!
Wilman said on June 8, 2011 at 10:52 am:

Thanks,

This saved my file configs to integration with other modules without affecting any of them with RESOURCE_LOCAL. Projects jbpm5.1 with jbosssa 5.1, postgres 9.0.
Kevin said on August 4, 2011 at 2:07 pm:

yes, it helped me.
thanks for posting.
Hari said on November 9, 2011 at 4:42 am:

Thanks a lot.
Vijay Jayaram said on December 15, 2011 at 1:19 am:

Thanks a lot Greg
This works
geeky Heather said on April 26, 2012 at 2:21 pm:

You are, quite literally, my hero.
andrea said on May 28, 2012 at 8:25 am:

it works also on JBoss 4.2.2. Thanks!
Danilo said on July 25, 2012 at 10:06 am:

JBoss 5.1.2 and running!
Perfect
Prashant said on August 2, 2012 at 7:01 am:

Thanks a lot…..