JdbcRetryException on Propagation.REQUIRED [DATAJDBC-86]

[spring-projects-issues]

Alexander K. opened DATAJDBC-86 and commented

Hi,
JdbcRetryException is thrown saying "An active transaction was found. This is not allowed when starting a retryable operation." even if @Transactional propagation value is REQUIRED. But in this case if there is an active transaction, then a new transaction will not be created. Hence JdbcRetryException should not be thrown and the retry should be done on the first created transaction

---

Affects: Ext 1.2 RELEASE

[spring-projects-issues]

Thomas Risberg commented

You'll have to provide some more context here. What are you trying to do? The RAC retry logic requires that it controls the transaction from start to finish, so we can't attach to an existing transaction

[spring-projects-issues]

Alexander K. commented

But this is the idea of REQUIRED propagation to attach to an existing transaction. And yes, in this case I would expect that the retry will be done on the first active transaction.
For example: let's assume we have 2 services A and B both of them @Transactional(propagation = Propagation.REQUIRED). If A or B were invoked as a standalone service, then we are fine. But if A invokes B because of service reuse, then the expectation is to attach B to the A's transaction and in case of failure - retry the whole service A

[spring-projects-issues]

Thomas Risberg commented

You would have to change your aop-config to only select the method of service A as the target for the rac-failover-interceptor. You can't nest these, there is no support for attaching to an existing interceptor

[spring-projects-issues]

Alexander K. commented

If I add rac-failover-interceptor to service A, then service B will be missing the failover support. I think that supporting REQUIRED propagation is very useful feature and as you said it is missing

[spring-projects-issues]

Thomas Risberg commented

You can't have an on-going active transaction for a retry operation since we can't wrap the original transaction with the retry logic, we have to create and wrap the transaction with the retry logic as it is created. That's just a restriction for this retry operation.

This is an old issue and will be closed, please re-open as GitHub issue (https://github.com/spring-projects/spring-data-jdbc-ext) if necessary