Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

one beanfactory can not have more than one TransactionManager when low memory [SPR-14706] #19271

spring-projects-issues opened this issue Sep 13, 2016 · 1 comment
in: data status: duplicate


Copy link

@spring-projects-issues spring-projects-issues commented Sep 13, 2016

qxo opened SPR-14706 and commented

sample code :

git clone

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:

  • #19177 Transaction manager cache fails to repopulate when multiple transaction managers defined ("duplicates")
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Sep 13, 2016

Juergen Hoeller commented

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
in: data status: duplicate
None yet

No branches or pull requests

2 participants