Wrong TransactionManager selected when mixing @Transactional with and w/o qualifier [SPR-12606]

[spring-projects-issues]

Alexander Imfeld opened SPR-12606 and commented

When using multiple TransactionManagers and declarative transaction management with @Transactional (with and w/o qualifier) and @EnableTransactionManagement, the TransactionInterceptor will lookup and store the default transaction manager in TransactionAspectSupport#determineTransactionManager in case there is no qualifier. This TransactionManager will then also be used in case there actually is a qualifier (as soon as a transactionManager is set it in determineTransactionManager, it will be used for all further calls).

Seems to me it's not possible to have multiple TransactionManagers (e.g. 'transactionManager' and 'anotherTransactionManager) and mix qualified with non-qualified Transactional annotations (e.g. @Transactional and @Transactional("anotherTransactionManager"))

Shouldn't qualifier based TransactionManager lookup be the primary mechanism to determine the TransactionManager in TransactionAspectSupport?

---

Affects: 4.1.3

Issue Links:

• DATAJPA-657 TransactionManager reference is ignored when using Spring 4.1.4
• @Transactional qualifier is ignored by TransactionAspectSupport if default transaction manager is set [SPR-12541] #17145 @Transactional qualifier is ignored by TransactionAspectSupport if default transaction manager is set
• Regression in TransactionAspectSupport.determineTransactionManager(…) [SPR-12577] #17178 Regression in TransactionAspectSupport.determineTransactionManager(…)

[spring-projects-issues]

Juergen Hoeller commented

I suppose this has been fixed along with #17145 for the 4.1.4 release already. Please upgrade to 4.1.4 and double-check that...

Note that there has been a side effect of that 4.1.4 fix which has been fixed for the upcoming 4.1.5 (#17178) and is available in recent 4.1.5 snapshots. Please try such a snapshot in case any problems remain with 4.1.4 for you.

Juergen