Skip to content
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

Spring Redis Session - TTL gets reset back to original timeout when deleteSession attempt is made #3184

Open
dreamstar-enterprises opened this issue Sep 1, 2024 · 1 comment
Labels
status: waiting-for-triage An issue we've not yet triaged type: bug A general bug

Comments

@dreamstar-enterprises
Copy link

dreamstar-enterprises commented Sep 1, 2024

I'm not sure if this is expected behaviour, but if my session timeout is 5 minutes the timeout on the hashed key is 10 minutes (an extra 5 minutes)

However, when I try to delete a key, the key remains and only the lastAccessedTime is left in there. However the ttl gets reset to 5 / 10 minutes again.

Is that expeced behaviour? Would seem strange when trying to invalidate a 6 hour long session, with 1 hour left for it to get reset back to 6 hours again?

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior.

Expected behavior
A clear and concise description of what you expected to happen.

Sample

A link to a GitHub repository with a minimal, reproducible sample.

Reports that include a sample will take priority over reports that do not.
At times, we may require a sample, so it is good to try and include a sample up front.

@dreamstar-enterprises dreamstar-enterprises added status: waiting-for-triage An issue we've not yet triaged type: bug A general bug labels Sep 1, 2024
@dreamstar-enterprises
Copy link
Author

Screenshot 2024-09-01 at 17 00 24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting-for-triage An issue we've not yet triaged type: bug A general bug
Projects
None yet
Development

No branches or pull requests

1 participant