Spring - No EntityManager with actual transaction available for current thread - cannot reliably process persist call

Question

I get this error when trying to invoke  persist  method to save entity model to database in my Spring MVC web application  Can t really find any post or page in internet that can relate to this particular error  It seems like something s wrong with EntityManagerFactory bean but i m fairly new to Spring programming so for me it seems like everything is initialized fine and according to various tutorial articles in web   dispatcher-servlet xml   lt  xml version  1 0  encoding  UTF-8   gt   lt beans xmlns  http   www springframework org schema beans   xmlns xsi  http   www w3 org 2001 XMLSchema-instance  xmlns mvc  http   www springframework org schema mvc   xmlns context  http   www springframework org schema context   xmlns jpa  http   www springframework org schema data jpa  xsi schemaLocation    http   www springframework org schema mvc   http   www springframework org schema mvc spring-mvc-4 0 xsd  http   www springframework org schema beans   http   www springframework org schema beans spring-beans-4 0 xsd  http   www springframework org schema context    http   www springframework org schema context spring-context-4 0 xsd   http   www springframework org schema jdbc   http   www springframework org schema jdbc spring-jdbc-3 2 xsd   http   www springframework org schema data jpa   http   www springframework org schema data jpa spring-jpa-1 3 xsd   http   www springframework org schema data repository   http   www springframework org schema data repository spring-repository-1 5 xsd   http   www springframework org schema jee   http   www springframework org schema jee spring-jee-3 2 xsd  gt        lt context component-scan base-package  wymysl Controllers    gt       lt jpa repositories base-package  wymysl repositories   gt        lt context component-scan base-package  wymysl beans    gt        lt context component-scan base-package  wymysl Validators    gt        lt bean      class  org springframework orm jpa support PersistenceAnnotationBeanPostProcessor    gt        lt bean class  org springframework orm hibernate4 HibernateExceptionTranslator   gt         lt bean id  passwordValidator  class  wymysl Validators PasswordValidator  gt  lt  bean gt         lt bean id  dataSource          class  org springframework jdbc datasource DriverManagerDataSource  gt            lt property name  driverClassName  value  oracle jdbc driver OracleDriver    gt           lt property name  url  value  jdbc oracle thin  localhost 1521 xe    gt           lt property name  username  value  system    gt           lt property name  password  value  polskabieda1    gt       lt  bean gt     lt bean id  entityManagerFactory  class  org springframework orm jpa LocalContainerEntityManagerFactoryBean  gt       lt property name  persistenceXmlLocation  value  classpath   META-INF persistence xml    gt       lt property name  dataSource  ref  dataSource    gt        lt property name  jpaVendorAdapter  gt           lt bean class  org springframework orm jpa vendor HibernateJpaVendorAdapter  gt               lt property name  databasePlatform  value  org hibernate dialect H2Dialect    gt               lt property name  showSql  value  true    gt               lt property name  generateDdl  value  false    gt           lt  bean gt       lt  property gt       lt property name  jpaProperties  gt           lt props gt               lt prop key  hibernate max fetch depth  gt 3 lt  prop gt               lt prop key  hibernate jdbc fetch size  gt 50 lt  prop gt               lt prop key  hibernate jdbc batch size  gt 10 lt  prop gt           lt  props gt       lt  property gt   lt  bean gt        lt mvc annotation-driven   gt        lt bean id  messageSource  class  org springframework context support ReloadableResourceBundleMessageSource  gt       lt property name  basename  value  classpath messages    gt   lt  bean gt        lt bean name  transactionManager  class  org springframework orm jpa JpaTransactionManager  gt                lt property name  entityManagerFactory  ref  entityManagerFactory   gt       lt  bean gt         lt bean class  org springframework web servlet view InternalResourceViewResolver  gt       lt property name  prefix  gt           lt value gt  WEB-INF jsp  lt  value gt       lt  property gt       lt property name  suffix  gt           lt value gt  jsp lt  value gt       lt  property gt   lt  bean gt        lt mvc resources mapping   resources     location   resources     gt       lt mvc resources mapping   resources    location   resources css         cache-period  31556926   gt      lt  beans gt    RegisterController java   Controller public class RegisterController         PersistenceContext     EntityManager entityManager        Autowired     PasswordValidator passwordValidator        InitBinder     private void initBinder WebDataBinder binder            binder setValidator passwordValidator               RequestMapping value     addUser   method   RequestMethod GET      public String register Person person              return  register                RequestMapping value     addUser   method   RequestMethod POST      public String register  ModelAttribute  person    Valid  Validated Person person  BindingResult result            if result hasErrors                  return  register             else               entityManager persist person               return  index

User · Answer

Adding the org springframework transaction annotation Transactional annotation at the class level for the test class fixed the issue for me

User · Answer

I had this issue for days and nothing I found anywhere online helped me  I m posting my answer here in case it helps anyone else   In my case  I was working on a microservice being called through remoting  and my  Transactional annotation at the service level was not being picked up by the remote proxy   Adding a delegate class between the service and dao layers and marking the delegate method as transactional fixed this for me

User · Answer

Just a note for other users searching for answers for thie error  Another common issue is      You generally cannot call an  transactional method from within the same class     There are ways and means using AspectJ but refactoring will be way easier   So you ll need a calling class and class that holds the  transactional methods

User · Answer

This error had me foxed for three days  the situation I faced produced the same error  Following all the advice I could find  I played with the configuration but to no avail   Eventually I found it  the difference  the Service I was executing was contained in a common jar  the issue turned out to be AspectJ not treating the Service instantiation the same  In effect the proxy was simply calling the underlying method without all the normal Spring magic being executed before the method call   In the end the  Scope annotation placed on the service as per the example solved the issue    Service  Scope proxyMode   ScopedProxyMode INTERFACES   Transactional public class CoreServiceImpl implements CoreService        PersistenceContext     protected EntityManager entityManager        Override     public final  lt T extends AbstractEntity gt  int deleteAll Class lt T gt  clazz            CriteriaDelete lt T gt  criteriaDelete   entityManager getCriteriaBuilder   createCriteriaDelete clazz           criteriaDelete from clazz           return entityManager createQuery criteriaDelete  executeUpdate               The method I have posted is a delete method but the annotations affect all persistence methods in the same way   I hope this post helps someone else who has struggled with the same issue when loading a service from a jar

User · Answer

This helped us  maybe it can help others in the future   Transaction was not working for us  but this did    ConditionalOnMissingClass  org springframework orm jpa JpaTransactionManager

User · Answer

I had the same error because I switched from XML- to java-configuration   The point was  I didn t migrate  lt tx annotation-driven  gt  tag  as Stone Feng suggested   So I just added  EnableTransactionManagement as suggested here Setting Up Annotation Driven Transactions in Spring in  Configuration Class  and it works now

User · Answer

I had the same error when accessing an already  transactional-annotated method from a non-transactional method within the same component   Before       Component     public class MarketObserver            PersistenceContext unitName    maindb           private EntityManager em            Transactional value    txMain   propagation   Propagation REQUIRES NEW          public void executeQuery               em persist                             Async         public void startObserving               executeQuery       lt -- Wrong                        In another bean       marketObserver startObserving      I fixed the error by calling the executeQuery   on the self-referenced component   Fixed version       Component     public class MarketObserver            PersistenceContext unitName    maindb           private EntityManager em            Autowired         private GenericApplicationContext context            Transactional value    txMain   propagation   Propagation REQUIRES NEW          public void executeQuery               em persist                             Async         public void startObserving               context getBean MarketObserver class  executeQuery       lt -- Works

User · Answer

Without  Transactional annotation you can achieve the same goal with finding the entity from the DB and then removing that entity you got from the DB  CrudRepositor - gt  void delete T var1

User · Answer

I removed the mode from    lt tx annotation-driven mode  aspectj  transaction-manager  transactionManager    gt    to make this work

User · Answer

For anyone with the same issue as I had  I was calling a public method method1 from within another class  method1 then called another public method method2 within the same class  method2 was annotated with  Transactional  but method1 was not  All that method1 did was transform some arguments and directly call method2  so no DB operations here  The issue got solved for me once I moved the  Transactional annotation to method1  Not sure the reason for this  but this did it for me

User · Answer

For us  the problem came down to same context settings in multiple configuration files   Check you ve not duplicated the following in multiple config files    lt context property-placeholder location  classpath   module properties   gt   lt context component-scan base-package          gt

User · Answer

I had the same problem and I annotated the method as  Transactional and it worked   UPDATE  checking the spring documentation it looks like by default the PersistenceContext is of type Transaction  so that s why the method has to be transactional  http   docs spring io spring docs current spring-framework-reference html orm html       The  PersistenceContext annotation has an optional attribute type    which defaults to PersistenceContextType TRANSACTION  This default is   what you need to receive a shared EntityManager proxy  The   alternative  PersistenceContextType EXTENDED  is a completely   different affair  This results in a so-called extended EntityManager    which is not thread-safe and hence must not be used in a concurrently   accessed component such as a Spring-managed singleton bean  Extended   EntityManagers are only supposed to be used in stateful components   that  for example  reside in a session  with the lifecycle of the   EntityManager not tied to a current transaction but rather being   completely up to the application

User · Answer

I had the same error code when I used  Transaction on a wrong method actionlevel    methodWithANumberOfDatabaseActions         methodA          methodA           Transactional void methodA               ERROR message     I had to place the  Transactional just above the method methodWithANumberOfDatabaseActions    of course   That solved the error message in my case

User · Answer

I got the same error when I executed the Spring JPA deleteAll   method from Junit test cases  I simply used the deleteInBatch    amp  deleteAllInBatch   and its perfectly works  We do not need to mark  Transactional at the test cases level

User · Answer

I got this exception while attempting to use a deleteBy custom method in the spring data repository  The operation was attempted from a JUnit test class   The exception does not occur upon using the  Transactional annotation at the JUnit class level

User · Answer

I had the same problem and I added tx annotation-driven in applicationContext xml and it worked

User · Answer

boardRepo deleteByBoardId id    Faced the same issue  GOT javax persistence TransactionRequiredException  No EntityManager with actual transaction available for current thread  I resolved it by adding  Transactional annotation above the controller service

User · Answer

If you have    Transactional    Spring Transactional class MyDao extends Dao       and super-class  class Dao       public void save Entity entity    getEntityManager   merge entity         and you call   Autowired MyDao myDao  myDao save entity     you won t get a Spring TransactionInterceptor  that gives you a transaction    This is what you need to do    Transactional  class MyDao extends Dao       public void save Entity entity    super save entity         Unbelievable but true

[java] Spring - No EntityManager with actual transaction available for current thread - cannot reliably process 'persist' call

Examples related to java

Examples related to spring

Examples related to spring-mvc

Examples related to web-applications