This seems like essentially the same issue as #19177, with a given PlatformTransactionManager weakly stored and failing to repopulate when more than one transaction manager bean is available.
Please give a recent 4.3.3.BUILD-SNAPSHOT a try and let me know if it fixes the problem for you...
qxo opened SPR-14706 and commented
sample code :
git clone https://github.com/qxo/spring-pull-1661-test
cd /spring-pull-1661-test
mvn test
===> will found the bug!
and fix pull : #1161
then setTransactionManagerBeanName on spring config (TransactionProxyFactoryBean) will slove the issue.
Issue Links:
The text was updated successfully, but these errors were encountered: