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

Activation expiration can lead to a deadlock on MSSQL #1626

Open
romanstrobl opened this issue Jul 27, 2024 · 2 comments
Open

Activation expiration can lead to a deadlock on MSSQL #1626

romanstrobl opened this issue Jul 27, 2024 · 2 comments
Assignees
Labels

Comments

@romanstrobl
Copy link
Member

When a concurrent update occurs due to activation expiration, this situation can lead to a deadlock on MSSQL, similar to the situation described in issue #1609.

Deadlock scenario:

  • UPDATE due to background expiration of an activation
  • UPDATE due to expiration of an activation due to request for an activation list, activation status, activation lookup, etc.
@romanstrobl romanstrobl self-assigned this Jul 27, 2024
@romanstrobl
Copy link
Member Author

Another problem with concurrency during activation expirations from a background job and a service call triggered by REST a API call is that callbacks are executed twice in case of concurrent expiration of an activation.

@OliverJanstaWultra
Copy link
Member

We couldn't reproduce this issue, but we will keep it open for a while if the issue occurs somewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants