New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DeadlockLoserDataAccessException during JdbcLock.unlock #3294
Comments
I think I agree with your suggestion: indeed we can retry such an operation until success with no exceptions. Feel free to raise a Pull Request. Although keep in mind that we are going to release tomorrow, not |
Fixes #3294 A `DeadlockLoserDataAccessException` occurs at `JdbcLockRegistry$JdbcLock.unlock()` - better to retry like in the `lock()` **Cherry-pick to 5.3.x, 5.2.x, 5.1.x & 4.3.x**
Fixes #3294 A `DeadlockLoserDataAccessException` occurs at `JdbcLockRegistry$JdbcLock.unlock()` - better to retry like in the `lock()` **Cherry-pick to 5.3.x, 5.2.x, 5.1.x & 4.3.x**
Fixes #3294 A `DeadlockLoserDataAccessException` occurs at `JdbcLockRegistry$JdbcLock.unlock()` - better to retry like in the `lock()` **Cherry-pick to 5.3.x, 5.2.x, 5.1.x & 4.3.x**
Fixes #3294 A `DeadlockLoserDataAccessException` occurs at `JdbcLockRegistry$JdbcLock.unlock()` - better to retry like in the `lock()` **Cherry-pick to 5.3.x, 5.2.x, 5.1.x & 4.3.x**
Hi @artembilan, |
July 22: https://github.com/spring-projects/spring-integration/milestone/37 Just after Spring Framework |
A DeadlockLoserDataAccessException occurs at org.springframework.integration.jdbc.lock.JdbcLockRegistry$JdbcLock.unlock(JdbcLockRegistry.java:236)
I'm using the 4.3.19 release but no unlock() retrying is present in newer releases.
Could it be possible to retry unlock() in case of TransientDataAccessException like lock()?
Thank you in advance!
The text was updated successfully, but these errors were encountered: