Shared EntityManager's target lookup doesn't work with Spring Data's ChainedTransactionManager [SPR-14371]

[spring-projects-issues]

Sathishkumar Murugesan opened SPR-14371 and commented

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 #17834. 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 #17834( #18411). 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.
.

---

Affects: 4.2.1, 4.2.5, 4.2.6, 4.3 GA

Reference URL: http://stackoverflow.com/questions/34494754/upgraded-from-spring-4-1-6-to-4-2-4-and-suddenly-getting-transactionrequiredexce

Issue Links:

• #18411 Regression: Shared EntityManager proxy insists on actualTransactiveActive flag even with SYNCHRONIZATION_NEVER
• #16541 Shared EntityManager should immediately throw TransactionRequiredException if no transaction in progress
• #17834 Inconsistent JPA behavior using no transaction, propagation SUPPORTS and OpenEntityManager pattern
• DATACMNS-803 ChainedTransactionManager does not work with latest spring

[spring-projects-issues]

Juergen Hoeller commented

I'm afraid this works as designed from the core framework's perspective, in particular with the recent refinements in #17834. Let's sort this out in the associated Spring Data ticket instead.