Skip to content

Session clean up job creating deadlocks #1922

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

Closed
davtrinh opened this issue Oct 7, 2021 · 1 comment
Closed

Session clean up job creating deadlocks #1922

davtrinh opened this issue Oct 7, 2021 · 1 comment

Comments

@davtrinh
Copy link

davtrinh commented Oct 7, 2021

Hi all,

This issue seems related to the issue #838.

The query that is giving us deadlock problems is:
UPDATE SPRING_SESSION SET SESSION_ID = ? LAST_ACCESS_TIME = ? MAX_INACTIVE_INTERVAL = ? EXPIRY_TIME = ? PRINCIPAL_NAME = ? WHERE PRIMARY_ID = ?

This ONLY happens in our production environment and we're not able to replicate it in our test environment. Both environment should be identical, and prod and test were created using the same snapshot.

We were on Spring version 2.3.10 RELEASE, but upgraded to 2.5.5 in hopes that the latest update would solve the issue, but it didn't. Our application is being deployed through ECS AWS and we're only running one instance of our application both on test/prod.

For now is there more documentation on how to disable the clean up job?

Affects: <Spring Framework version>


@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Oct 7, 2021
@davtrinh
Copy link
Author

Ended up just using spring redis with AWS elasticache to replace it instead

@eleftherias eleftherias added status: invalid and removed status: waiting-for-triage An issue we've not yet triaged labels Nov 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants