Transaction manager cache fails to repopulate when multiple transaction managers defined [SPR-14609] #19177
Comments
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. |
Juergen Hoeller commented
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tim Lenz opened SPR-14609 and commented
When
TransactionAspectSupport
is initialized, the transaction manager cache is populated by thesetTransactionManager
method. At this point there can be multipleTransactionInterceptor
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 aNoUniqueBeanDefinitionException
if multiple transaction managers are defined in your application context.This is a regression caused by #19080.
Affects: 4.3.2
Issue Links:
The text was updated successfully, but these errors were encountered: