search

softwaremill / elasticmq

In-memory message queue with an Amazon SQS-compatible interface. Runs stand-alone or embedded.
https://softwaremill.com/open-source/
Apache License 2.0
2.52k stars 193 forks source link

404s after updating AWS SDKs #986

Closed OliverTaggart closed 3 months ago

OliverTaggart commented 6 months ago

After upgrading our project's aws-java-sdks from 1.12.565 to 1.12.638 we're seeing the following error with elasticmq queues: Exception happened when try to receive messages from queue - com.amazonaws.services.sqs.model.AmazonSQSException: null (Service: AmazonSQS; Status Code: 404; Error Code: null; Request ID: null; Proxy: null) 09:28:24 user ERROR c.l.u.s.p.<OurProcessor> 525588613033092391 Failed to receive message from queue: http://localhost:9324/queue/<our-queue>+ Cause: null (Service: AmazonSQS; Status Code: 404; Error Code: null; Request ID: null; Proxy: null)

Upgrading our version of elasticmq to 1.4.2 (we're currently on 0.13.10 :skull: ) doesn't solve the issue, either. I'm wondering if there's some dependency I need to add to our project, or some other obvious gotcha that I'm missing. The last time anyone touched our elasticmq implementation was 6 years ago.

We manage our elasticmq version via a chef cookbook, and manage our dependencies with maven.

kirangubbi commented 3 months ago

we are facing the same issue after upgrading aws-java-sdks from 1.12.565 to 1.12.638. Why has this issue #986 been changed to not planned?

OliverTaggart commented 3 months ago

I should have left a comment when closing (and maybe closed the issue as something other than 'not planned'). Our issue was the elasticmq upgrade wasn't being applied properly. After successfully upgrading and applying the latest version of elasticmq, we no longer saw the error. I'll leave it to @micossow to re-close or investigate as needed.

micossow commented 3 months ago

@kirangubbi are you using the latest version w ElasticMQ? The latest version is tested against SDK 1.12.699. If you have any issues with the latest version, I would need more details to reproduce the issue.

kirangubbi commented 3 months ago

Thanks for the updates. I tried upgrading aws-java-sdks to1.12.750 and elasticmq-rest-sqs to 1.6.5 but failed with the some date format issue. Then I changed elasticmq-rest-sqs to 1.5.3. It worked.

micossow commented 3 months ago

Is that some date format issue related to ElasticMQ?

kirangubbi commented 3 months ago

I am not entirely sure if it relates to ElasticMQ. I just went for 1.5.3 because after that version it has additional support for scala 3 which I thought might be causing this issue.

micossow commented 3 months ago

Ok, I'll close the issue then.