Hi everyone,
We’ve just released ServiceControl 4.21.3.
Fixed bugs
- #2745 When endpoints use the legacy Azure Service Bus transport, upgrading ServiceControl to 4.21, 4.21.1, or 4.21.2 can cause deserialization exceptions resulting in metrics/heartbeat/customcheck/saga audit messages being sent to the error queue
How to know if you are affected
You are affected if your ServiceControl or ServiceControl monitoring instances have been upgraded to version 4.21, 4.21.1, or 4.21.2, and your system has endpoints where the following are true:
- They are using the legacy
NServiceBus.Azure.Transports.WindowsAzureServiceBustransport. - They have not configured the
BrokeredMessagebody format to use the stream format. - They are using one or more of the following packages:
- NServiceBus.Metrics.ServiceControl
- NServiceBus.Metrics.ServiceControl.Msmq
- NServiceBus.Heartbeat
- NServiceBus.CustomChecks
- NServiceBus.SagaAudit
Be aware that communication between endpoints using the legacy NServiceBus.Azure.Transports.WindowsAzureServiceBus transport and endpoints using the NServiceBus.Transport.AzureServiceBus transport version 2.0.1 may be similarly impacted, which has been addressed in a critical patch for the NServiceBus.Transport.AzureServiceBus transport.
Symptoms
Depending on the serializer used, non-user defined messages may appear in ServicePulse / ServiceInsight with a deserialization exception. Here is an example when using NewtonsoftSerializer:
NServiceBus.MessageDeserializationException: An error occurred while attempting to extract logical messages from incoming physical message 00000000-0000-0000-0000-000000000000 --->
Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: @. Path '', line 0, position 0.
When to upgrade
You should upgrade immediately if your system is affected.
Where to get it
You can download the new version of ServiceControl from our website.
With thanks,
The team in Particular
Please read our support policy for more details.