- Newest
- Most votes
- Most comments
You don't say whether you're specifying the MessageGroupId
or not when sending the message so I'm going to assume for a moment that you're using a single group id.
Looking at the documentation for FIFO delivery logic what happens is that the ReceiveMessage
call gets the number of messages you ask for (default is 1, maximum is 10) and then will not receive any more messages from the same group id until those message(s) have been deleted or are visible again. This is to ensure that messages are delivered in the correct order - which is what FIFO queues offer.
You can have multiple messages in flight if you use multiple group ids - but then ordering is only within the groups rather than the queue as a whole. Then you can have as many messages in flight (assuming you get one at a time) as you have unique group ids.
If ordering isn't important then a non-FIFO queue might be the way to go.
Apologies, I'm not sure how to close the question. My mistake was that I was sending the same MessageGroupId for every message to this queue, when in fact I shouldn't have. This allows multiple processors to consume the queue.
Relevant content
- asked 2 years ago
- asked 2 months ago
- asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 4 months ago
thank you, just as I realised this myself I saw your answer :)