Command timed out if execute multi/exec in readonly database transaction [DATAREDIS-988]

[spring-projects-issues]

Yanming Zhou opened DATAREDIS-988 and commented

1. enableTransactionSupport = false
2. works fine with @Transactional(readOnly=false) but failed with readOnly=true, monitor redis commands, exec is not received by redis-server if readOnly=true

---

Affects: 2.1.8 (Lovelace SR8)

Attachments:

• redis-tx.zip (3.34 kB)

Issue Links:

• DATAREDIS-548 Connection should be released when used with read-only transactions

Referenced from: pull request #453

Backported to: 2.1.10 (Lovelace SR10)

[spring-projects-issues]

Mark Paluch commented

When running commands in a SessionCallback within a read-only transaction, then the connection gets unbound after the first call. This was initially intended to not attach synchronizations to the transaction.

There's also another issue, when obtaining a connection, we always set the database. When the connection is in transactional state, we also issue a SELECT command that never completes because EXEC was not yet called. The transaction is in MULTI state because the state was not reset when the connection was released back to the pool