Hi everyone,
We’ve just released NServiceBus.Persistence.AzureTable 7.0.1, 6.1.2, and 5.0.4.
Fixed bugs
- #1116 Endpoints using the outbox subscribed to the same event will experience concurrency conflicts if sharing the same outbox table
How to know if you are affected
You are affected if:
- You have multiple subscribers handling the same published event
- You have not overridden the default partition key to be unique per subscribing endpoint
- All endpoints are sharing the same outbox table (which is the default behavior)
Symptoms
You see log errors similar to the following:
7:47:47 AM Info SubscribersHandlesTheSameEvent.Subscriber2: Immediate Retry is going to retry message '91cebc6e-169b-4ca1-8ccf-b35300807ba2' because of an exception:
Azure.Data.Tables.TableTransactionFailedException:
0:The update condition specified in the request was not satisfied.
RequestID:b65b4abe-22bc-4794-8b07-6c5ee1575889
The index of the entity that caused the error can be found in FailedTransactionActionIndex.
Status: 412 (Precondition Failed)
ErrorCode: UpdateConditionNotSatisfied
Additional Information:
FailedEntity: 0
Service request succeeded. Response content and headers are not included to avoid logging sensitive data.
When to upgrade
You should upgrade immediately if you are affected. Otherwise, you should upgrade during your next maintenance window.
Where to get it
You can install the new versions of NServiceBus.Persistence.AzureTable from NuGet.
Please read our release policy for more details.
With thanks,
The team in Particular