InvalidChecksum: sendMessage returned an invalid MD5 response.

[John Barton]

Hi,

I've tried the following with the latest released version (0.8.2) and the latest code (commit SHA 67d217b44f95348ec7937dc552ad09c189200ebd).

I'm using the NodeJS aws-sdk in a NodeJS application. It is sending a large volume of messages to 1 queue (approx 22k messages). I've tried sending them asynchronously, as well as 1 at a time and both methods fail.

Every time it fails with the following error (different MD5 hashes each time):

"sendMessage returned an invalid MD5 response. Got "df2bc53e03f1bb6960d440b850f5c754", expecting "a4cca62be1778904276d964803ec1aab"."

It doesn't fail on the same message every time, which makes me think it could be a race condition.

Has anyone seen this before? I am hoping its my set-up, as I'm assuming someone else would have spotted something like this before now! Note that it works fine when using the *real* AWS SQS

Thanks in advance

John

[John Barton]

So, I tried to isolate the problem and narrowed it down to the data I passing to the MessageBody in the SendMessage call.

I was importing a large feed from a 3rd party - and I wasn't escaping the data in the JSON. As soon as I did - the problem went away.

I will try to narrow down to a particular message that causes the problem

[Adam Warski]

If you could find some way to reproduce this bug reliably, it would be great.

There were several reports of this occurring, but I never managed to create a test case.

Thanks!

Adam

--

---
You received this message because you are subscribed to the Google Groups "ElasticMQ" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticmq+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

-- 
Adam Warski

http://twitter.com/#!/adamwarski
http://www.softwaremill.com
http://www.warski.org