Uploaded image for project: 'Spring Framework'
  1. Spring Framework
  2. SPR-14609

Transaction manager cache fails to repopulate when multiple transaction managers defined

    XMLWordPrintable

    Details

    • Last commented by a User:
      true

      Description

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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              juergen.hoeller Juergen Hoeller
              Reporter:
              seabamirum Tim Lenz
              Last updater:
              Spring Issues Spring Issues
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since last comment:
                3 years, 24 weeks, 1 day ago