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

Written by

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.(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)

Second make sure we have following line under properties node

Thats it, I hope this helps someone.

Comments

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

February 26, 2010

essnet

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!

Reply
March 13, 2010

azzuwan

Thanks Greg, it works for me too

Reply
1. March 17, 2010
  
  Greg
  
  I’m happy that this is useful to some people.
  
  Reply
May 22, 2010

Leandro Bortolotto

Thanks Greg and essnet, it works on glassfish v3 for me too.

Reply
May 31, 2010

Robert Moore

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?

Reply
July 21, 2010

Vasko Gjurovski

Robert, I have the same problem. Did you manage to find a solution for it?

Reply
August 18, 2010

Zabin

Thanks Greg…. It helped a lottttttttttttttt

Reply
October 16, 2010

Vitorino

Man, thanks a lot! You saved me from a big headache! I really really appreciate it! Kudos for your post!

Reply
October 19, 2010

Ingvar Larsson

Well, I also want to say thanks!!! Very very helpful!!

Reply
February 23, 2011

Aksel

Thanks!
This saved my day!
Im deploying on JBoss 6.0.0 Final

Reply
1. February 23, 2011
  
  Greg
  
  Happy to hear that.
  
  Reply
April 24, 2011

corota

Thank you for your help!!

Reply
June 8, 2011

Wilman

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.

Reply
August 4, 2011

Kevin

yes, it helped me.
thanks for posting.

Reply
November 9, 2011

Hari

Thanks a lot.

Reply
December 15, 2011

Vijay Jayaram

Thanks a lot Greg
This works
😉

Reply
April 26, 2012

geeky Heather

You are, quite literally, my hero.

Reply
May 28, 2012

andrea

it works also on JBoss 4.2.2. Thanks!

Reply
July 25, 2012

Danilo

JBoss 5.1.2 and running!
Perfect

Reply
August 2, 2012

Prashant

Thanks a lot…..

Reply