Transaction manager cache fails to repopulate when multiple transaction managers defined [SPR-14609]

[spring-projects-issues]

Tim Lenz opened SPR-14609 and commented

When TransactionAspectSupport is initialized, the transaction manager cache is populated by the setTransactionManager method. At this point there can be multiple TransactionInterceptor instances defined, each with its own cache, with no conflicts.

However, as soon as the transaction cache entry in TransactionAspectSupport is cleared by the garbage collector, the transaction manager bean is then looked up by type, which leads to a NoUniqueBeanDefinitionException if multiple transaction managers are defined in your application context.

This is a regression caused by #19080.

---

Affects: 4.3.2

Issue Links:

• #19271 one beanfactory can not have more than one TransactionManager when low memory ("is duplicated by")
• #19080 Transaction manager bean in TransactionInterceptor retained after JUnit test class completes
• INT-4104 No qualifying bean of type [org.springframework.transaction.PlatformTransactionManager] is defined

[spring-projects-issues]

Juergen Hoeller commented

This is the trigger to undo #19080 for the (still unreleased) 4.2.8, whereas we'll try to fix it retaining #19080 for 4.3.3.

[spring-projects-issues]

Juergen Hoeller commented

TransactionAspectSupport stores a given PlatformTransactionManager instance as a strong reference (again) while retaining the soft cache for retrieved PlatformTransactionManager beans.