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.

Sign up for GitHub

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

Jump to bottom

Saga completion is ignored when the saga concurrently processes another message #262

Closed
SzymonPobiega opened this issue Mar 5, 2018 · 2 comments
Closed

Saga completion is ignored when the saga concurrently processes another message #262

SzymonPobiega opened this issue Mar 5, 2018 · 2 comments
Assignees
@SzymonPobiega
Labels
Bug
Milestone
3.0.5

Comments

@SzymonPobiega
Copy link
Member

Symptoms

One two messages arrive and are concurrently processed by a saga instance, if one of the messages updates the saga state while the other causes the saga completion, the completion is ignored if the update happens first. The completion (deleting of the saga row) is conditional on the version number. If the version number does not match (concurrent update), the row is not deleted but no exception is raised that would trigger the reprocessing of a message.

Who's affected

All users of SQL Persistence who use sagas.
@SzymonPobiega
Copy link
Member Author

Discourse thread #262
Fix #261

@SzymonPobiega SzymonPobiega self-assigned this Mar 5, 2018
@SzymonPobiega SzymonPobiega added this to the 3.0.5 milestone Mar 5, 2018
@SzymonPobiega
Copy link
Member Author

Fixed in hotifx-3.0.5. All builds green.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SzymonPobiega SzymonPobiega

Labels
Bug
Projects
None yet
Milestone
3.0.5
Development

No branches or pull requests
1 participant
@SzymonPobiega