ServiceControl 3.1.1 and 2.1.4 - Patch releases available

[Grendel (Edward Dewe)]

Hi Szymon - thanks for that. We have service control up and running under SQS. All the audit and error messages it is consuming are failing out to the servicecontrol poison/error queue with the following error:

2018-09-17 12:03:15.7536|76|Warn|NServiceBus.Transports.SQS.MessagePump|Treating message with SQS Message Id 4d6ee26c-ac3d-41a7-be4b-7099f2595b24 as a poison message due to exception Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: {. Path ‘ReplyToAddress’, line 1, position 1015.
_ at Newtonsoft.Json.JsonTextReader.ReadStringValue(ReadType readType)_

The majority of our business endpoints are still on AmazonSQS v1.3.1. Looks like Service Control is triggering this known bug:

NServiceBus.AmazonSQS 3.3.1/4.0.1/4.1.1 - Patch releases available

Hi everyone, We’ve just released NServiceBus.AmazonSQS 3.3.1/4.0.1/4.1.1. Fixed bugs #232 On the wire compatibility- subscriptions v5 - v7 fails on ReplyToAddress header How to know if you are affected When processing a message from an endpoint using version 1.x of the transport the messages fails on serialization with the following message: NServiceBus.Transports.SQS.MessagePump [(null)] - Treating message with SQS Message Id 8869dadb-a5e3-4722-a14c-7fd30858d4cc as a poison message due …

Looking at your Service Control SQS project for the 3.1.1 release you have not upgraded your SQS transport package to include the 4.1.1 patch:

Particular/ServiceControl/blob/3.1.1/src/ServiceControl.Transports.SQS/ServiceControl.Transports.SQS.csproj

Can you please update SC 3.1 to use 4.1.1 of the SQS transport?

Kind regards,

Edward