We’ve just released ServiceControl 3.6.6. This release addresses a bug in ServiceControl related to processing messages with an ID that contains characters that must be URL encoded.
- #1596 Message body of failed message is lost when messages contain Ids that have characters that must be URL encoded
When retrying the message in ServiceControl the log files have messages indicating the message body could not be retrieved:
2019-02-28 15:42:21.6943|73|Warn|ServiceControl.Recoverability.ReturnToSender|72802d3f-fa83-4088-8d02-8489a341c6e2\16410: Message Body not found for attempt Id 72802d3f-fa83-4088-8d02-8489a341c6e2\16389
Messages will be retried without their bodies leading to the endpoint processing the message without invoking messagehandlers.
Should you upgrade immediately
All users consuming messages where the message ID contains any characters that must be URL encoded. Unless you are overriding the message IDs generated by NServiceBus, the most common scenarios where this can happen involve integrations with 3rd party systems that send messages natively with non-conforming IDs and are processed by NServiceBus endpoints.
Where to get it
You can download the 3.6.6 release from our website.
The team in Particular
Please read our release policy for more details.