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

Handle scenario where compensating transaction returns a failure #75

Open
cer opened this issue May 30, 2022 · 0 comments
Open

Handle scenario where compensating transaction returns a failure #75

cer opened this issue May 30, 2022 · 0 comments

Comments

@cer
Copy link
Collaborator

cer commented May 30, 2022

Current behavor

} else if (compensating) {
throw new UnsupportedOperationException("Failure when compensating");

This breaks reply message handling.

What about happen:

  • The saga should transition to a failed state.
  • (Possible) the orchestration should tell the participant's command handling logic (via a header) to require a successful response.
cer added a commit that referenced this issue Jun 1, 2022
… Extracted common functionality out of non-reactive and reactive SagaDefinition, #77 Refactor to reduce copy/paste in SQL code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant