Allow Retrying QueueAttributes Fetching Failures

[tomazfernandes]

Discussed in #1234

^{Originally posted by jtglass1 September 25, 2024}
Hi guys. I've a strange issue which is intermittent and I wanted to see if you had come across this before or might know what is causing it. I've two apps - [a] Admin - which runs in one JVM in ECS which allows the user to create queues dynamically via your framework [b] Reception - server which runs in a many JVM cluster also in ECS - it takes messages inbound from a REST API uses headers to derive the SQS queue the message will be stored on, and writes to that queue. 99% of the time this all works - and when a new queue is created by Admin, reception is able to use it immediately. However, sometimes, when reception tries to write to a new queue, it cannot find it. All other queues continue to work and we've never seen the look-up of a queue start to fail when it worked previously - the issue only happens when trying to write to a new queue for the first time. Only by restarting the reception server does the look-up start to work. It feels like there is some sort of cache here which is - for some reason - not getting refreshed reliably. I don't know if the 'can't find queue' is coming from the Spring layers or the AWS layers. It is also possible that there is an attribute I can use when creating the queue which will solve this issue - something like 'force cache reset'. I'm using v 3.1.1. I've put this in discussion as I honestly don't know where to start - AWS issue or Spring Cloud issue. Hoping you might have a view, thanks!