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

Shared EntityManager's target lookup doesn't work with Spring Data's ChainedTransactionManager

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Works as Designed
    • Affects Version/s: 4.2.1, 4.2.5, 4.2.6, 4.3 GA
    • Fix Version/s: None
    • Component/s: Transaction
    • Labels:
      None

      Description

      If we have more than one TransactionManager involved, and If we invoke JmsTransactionManager first, followed by JPATransactionManager then JPATransactionManager is coming as null. which eventually breaks code.

      Exact Scenario is explained by Murali Mohan Rath : He raised a related bug at https://jira.spring.io/browse/DATACMNS-803

      Because of this issue we were not able to migrate from Spring 4.1.6 to any higher Spring Version

      This issue is already raised in SPR-13243. and latest comment from Juergen Hoeller below

      As for the target suddenly being null in some scenarios on 4.x, this seems to be a separate issue not caused by the changes behind SPR-13243( https://jira.spring.io/browse/SPR-13838). Let's create a separate JIRA issue for that scenario if it remains to be a problem.

      This issue is not still resolved in Spring 4.3.0 also.
      .

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. DATACMNS-803 ChainedTransactionManager does not work with latest spring

          • Major - Major loss of function.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. SPR-13838 Regression: Shared EntityManager proxy insists on actualTransactiveActive flag even with SYNCHRONIZATION_NEVER

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SPR-11923 Shared EntityManager should immediately throw TransactionRequiredException if no transaction in progress

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SPR-13243 Inconsistent JPA behavior using no transaction, propagation SUPPORTS and OpenEntityManager pattern

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

            Activity

              People

              Assignee:
              juergen.hoeller Juergen Hoeller
              Reporter:
              sathish.murugesan Sathishkumar Murugesan
              Last updater:
              Spring Issues Spring Issues
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

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