Skip to content

RedisOperationsSessionRepository fails with ERR no such key on concurrent session id change #1327

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
vpavic opened this issue Jan 29, 2019 · 0 comments
Assignees
Labels
in: redis type: backport An issue that is a backport of another issue to a maintenance branch type: bug A general bug
Milestone

Comments

@vpavic
Copy link
Contributor

vpavic commented Jan 29, 2019

Backport of #1270.

@vpavic vpavic added type: bug A general bug Data Store in: redis type: backport An issue that is a backport of another issue to a maintenance branch labels Jan 29, 2019
@vpavic vpavic added this to the 2.0.10 milestone Jan 29, 2019
@vpavic vpavic self-assigned this Jan 29, 2019
vpavic added a commit that referenced this issue Jan 29, 2019
In scenario with concurrent requests attempting to change session id, the "ERR no such key" error will occur for a thread that comes in second. This commit addresses the problem by ignoring the aforementioned error.

Resolves: #1327
@vpavic vpavic closed this as completed Jan 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: redis type: backport An issue that is a backport of another issue to a maintenance branch type: bug A general bug
Projects
None yet
Development

No branches or pull requests

1 participant