You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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>
The text was updated successfully, but these errors were encountered:
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>
The text was updated successfully, but these errors were encountered: