The Spring Framework offers an extensive API for database transaction management. Spring takes care of all basic transaction management control and provides a consistent programming model for different transaction APIs, such as JDBC, Hibernate, Java Transaction API (JTA), Java Persistence API (JPA), and Java Data Objects (JDO). There are two types of transactions provided by Spring: one is declarative and the other is programmatic transaction management. Declarative is very high-level, while programmatic is more advanced but flexible.

Spring transaction management works very well with a single thread. But it cannot manage a transaction across multiple threads. If we try to use the transaction with multiple threads, our program gives a runtime error or an unexpected result.

To understand why a Spring transaction fails with multiple threads, first, we need to understand how transactions work with Spring. Spring stores all transaction information in the ThreadLocal variables inside the org.springframework.transaction.support.TransactionSynchronizationManager class:

https://dzone.com/articles/spring-transaction-management-over-multiple-thread-1