Michał Ossowski

Hi, it's fixed in [1.3.13](https://github.com/softwaremill/elasticmq/releases/tag/v1.3.13) You can now use both `http://:/queueName` and `http://:/[a-zA-Z0-9]+/queueName` urls to access the queue. Also, the context path in config is now respected, respectively: `http://:/my-context/queueName` and...

Hi @rvanlaak, is the problem related to elasticmq in any way? It seems like you are not able to connect to elasticmq due to some problem with PHP SDK, which...

Ok, so answering your suggestions: 1. As you mentioned, any credentials passed to elasticmq are ignored and we won't change that behavior. 2. This is out of scope of this...

Hi @nicolasassi, if you want us to investigate the issue, please provide an application reproducing the problem, preferably in a form of GH repo, that we'd be able to run...

You can try with debug log messages from akka and elasticmq: ```xml ```

Well, that's how the SQS works. If you receive the message `maxReceiveCount` times, but don't delete it using [DeleteMessage](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_DeleteMessage.html), it gets moved to dead letter queue. SQS messages do not...

I fixed the `NonExistentQueue` error as a hotfix, however in order to completely solve the issue, the remaining errors need to be reviewed and adjusted for the new format.

@johncoleman83 can you provide an example of a specific request, that produces an invalid response and what is the expected response?

No, we do not plan to do that. Are you not able to access the images on Docker Hub?

Thanks, we'll add this to our tasks list.