Closed SeanFeldman closed 9 years ago
Anyone who's using multi-threaded sagas
When at least 3 threads access the same saga entity concurrently, then a specifc thread interleaving pattern can cause accepted updates with old data values that should have been rejected due to the wrong etag value assigned to the data entity.
Original issue: https://github.com/Particular/NServiceBus.Azure/issues/248
Who's affected
Anyone who's using multi-threaded sagas
Symptoms
When at least 3 threads access the same saga entity concurrently, then a specifc thread interleaving pattern can cause accepted updates with old data values that should have been rejected due to the wrong etag value assigned to the data entity.
Original issue: https://github.com/Particular/NServiceBus.Azure/issues/248