Whether it is safe to do it in your specific part code highly depends on what the code does.
Is there a way to mix these transactions safely or use the already Reading/writing same tables causing deadlocks. I think the problem is that there are two nested transactions Under the hood, Spring will do the same thing you would do manually to start and commit/rollback transactions. Declarative transactions enable you to demarcate transaction boundaries in a more concise and readable way, that's all about it. When it comes to the behavior of the transactions, there is really no difference between declarative and programmatic/manual ones.
Is there a way to mix these transactions safely or use the already started transaction in both? Should I just close the manually/programmatically opened transaction before calling Spring methods? Both Spring and HibernateUtil uses the same entity manager for database connections. Session db = HibernateUtil.getSessionFactory().openSession() I think the problem is that there are two nested transactions reading/writing same tables causing deadlocks.
#Declarative transaction management in spring hibernate software
The software has newer modules that are using Spring data architecture with declarative transactions We have experienced database deadlocks in rare cases with Microsoft SQL Server when newer Spring services are being called from inside "manually" opened transactions. I am developing a legacy software (Spring + Hibernate) that handles database connections and transactions in a programmatic fashion.
My question concerns about possible concurrency issues with mixing programmatic and declarative transactions.
0 kommentar(er)
