You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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:
The text was updated successfully, but these errors were encountered: