Hi everyone,
We’ve just released NServiceBus.Persistence.AzureTable 3.2.2, 4.0.1, and 5.0.1.
Fixed bugs
-
#752 Processing a control message causes the outbox to throw a
NullReferenceException
How to know if you are affected
You are affected if:
- You have the outbox enabled
- You are using a transport requiring message-driven (persistence-based) publish and subscribe or
- You are using callbacks with an integer or enum response
Symptoms
When the transport receives a control message, the partition key cannot be determined which leads to a NullReferenceException with a stack trace similar to the one below:
NServiceBus.ImmediateRetry[0]
Immediate Retry is going to retry message '14223e81-196b-4ee5-852c-5c5a3626462b\32009' because of an exception:
System.NullReferenceException: Object reference not set to an instance of an object.
at NServiceBus.Persistence.AzureTable.OutboxPersister.SetAsDispatched(String messageId, ContextBag context, CancellationToken cancellationToken) in /_/src/NServiceBus.Persistence.AzureTable/Outbox/OutboxPersister.cs:line 77
at NServiceBus.TransportReceiveToPhysicalMessageConnector.<Invoke>d__1.MoveNext() in /_/src/NServiceBus.Core/Pipeline/Incoming/TransportReceiveToPhysicalMessageConnector.cs:line 67
When to upgrade
You should upgrade immediately if you are affected.
Where to get it
You can install the new versions of NServiceBus.Persistence.AzureTable from NuGet.
With thanks,
The team in Particular
Please read our release policy for more details.