We’ve just released NServiceBus.AmazonSQS 4.3.2, 4.2.3, and 3.3.5.
- #291 Large message bodies encrypted with AWS-KMS cannot be received
How to know if you’re affected
Messages with large bodies are sent to S3, but when the transport tries to receive them it fails with messages such as:
2019-04-01 13:49:38.6062|31|Warn|NServiceBus.Transports.SQS.MessagePump|Treating message with SQS Message Id 456bd3cd-3720-408a-a2de-245c21e91e7d as a poison message due to exception System.NotSupportedException: This stream does not support seek operations. at System.Net.ConnectStream.get_Length() at NServiceBus.AmazonSQS.MessageExtensions.<ToIncomingMessage>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NServiceBus.Transports.SQS.MessagePump.<ProcessMessage>d__7.MoveNext(). Moving to error queue.
The messages are moved to the error queue but cannot be successfully retried because the transport will never be able to receive them.
Should you upgrade immediately
You should upgrade immediately if you need to use AWS-KMS encrypted S3 buckets to transfer oversize messages.
Where to get it
You can download the updated version directly from NuGet: https://www.nuget.org/packages/NServiceBus.AmazonSQS
The team in Particular