NServiceBus.AmazonSQS
NServiceBus.AmazonSQS copied to clipboard
Particular
An AWS SQS transport for NServiceBus.
The following PR resolved an obsolete compiler warning by suppressing it: - https://github.com/Particular/NServiceBus.AmazonSQS/pull/1707 The obsolete message: > [CS0618] 'IClientConfig.DetermineServiceURL()' is obsolete: 'This operation is obsoleted because as of version 3.7.100...
Currently, the transport does a number of things like [base64 encoding](#1446) and the [message type header requirement](https://docs.particular.net/transports/sqs/native-integration#message-type-detection) that makes it hard to use native messages. Ideally, we would flip around...
Or at the very least, get some docs up describing how to do it, linking those to things like our SQS Transport. I'd also suggest updating our AWS samples to...
[Should_route_commands_correctly: _1/nservicebus.acceptancetests.sources/8.0.0-rc.3/contentFiles/cs/net472/NSB.AcceptanceTests/Routing/When_using_custom_routing_strategy.cs#L21](https://github.com/Particular/NServiceBus.AmazonSQS/pull/1696/files#annotation_5599289383) > System.Exception : Delayed delivery queue 'ATXGPLVQRO70EBYOR39UCG7WUsingCustomRoutingStrategy-Receiver-delay.fifo' has a Delivery Delay of '00:00:00'. It should be less than '00:15:00'.
`Remove_large_message_support_from_endpoint_removes_bucket_with_remove_shared_resources`
When using the [unrestricted delayed delivery](https://docs.particular.net/transports/sqs/delayed-delivery) support, under certain circumstances (e.g., very long delay), the transport continuously re-schedules the delayed message very 15 minutes. Every re-schedule operation is a transaction...
The following is an excerpt from a ServiceControl log. An audit instance needs to send messages to a primary instance. The primary instance queue was not available. From the error...
Some of the acceptance tests are written in such a way, that they can suffer from SNS access policy propagation delays. These are tests where more than one manual `Subscribe`...
Currently, when the messages cannot be forwarded from SNS topics to SQS queues there are no traces of any errors. We could expose an option to enable CloudWatch watching e.g.:...
When the SQS transport was transferred to Particular, one aspect of the original design decisions that was baked into the transport was that queue creation was that endpoint queue creation...
