I have a question regarding visibility timeouts.
Setting the timeout on either message receive or setting it implicity with changeMessageVisibility doesn't appear to take effect. I have a test case that:
1. sends a message to a queue
2. retrieves the message with a visibility timeout of 1 second (I've tried with setting it implicitly too)
3. performs a long poll with anywhere up to 20 seconds to ensure the message isn't there
With ElasticMq the message is not available, but when I run the same test against real SQS it is.
Am I doing something wrong or is this an issue with ElasticMq?