We’ve just released NServiceBus.AmazonSQS 4.3.0.
- #102 - Use batched sends for multiple messages as long as payload fits size restrictions
- #239 - Make S3 configuration for large messages optional
- #187 - Error messages when configuration is bad are not helpful
- #258 - Propagate NSB Message ID as SQS Message Attribute
- #249 - Header manipulations done in recoverability policy are visible during next attempt to process a message
- #250 - Header manipulations done while processing a message are visible in recoverability policy
- #248 - Header manipulations persist between processing attempts
- #242 - Task.WhenAll in message pump can block receive operations
- #274 - Make NServiceBus aware of the native message id
- #189 - Switch from Newtonsoft.JSON to embedded SimpleJSON
- #280 - ToTransportAddress should generate a valid SQS queue address
How to know if you are affected
You are affected only if one or more of the above issues applies to you.
Should you upgrade immediately
This is a maintenance release for NServiceBus.AmazonSQS. It is not required to upgrade immediately unless you are affected by one of the issues listed above. Note that with the introduction of batched sends for messages sent out in the message handling pipeline, message throughput with the Amazon SQS transport should increase noticeably. Furthermore the risk of partial successful sends is significantly reduced due to messages getting batched together up to a maximum of ten depending on the message size.
Where to get it
You can download the updated version and see the full release notes here: https://github.com/Particular/NServiceBus.AmazonSQS/releases/tag/4.3.0
The team in Particular
Please read our release policy for more details.