#1 SQS msg body is always null in libaws; not null in AWS SDK

[Anonymous]

Trying to read a message off an SQS queue. Wrote a sample program to do it in PHP using AWSSDK. Works fine.

Modified libaws cli demo to do the same thing. LIbAWS sees the message on the queue, but when the message body is returned, the message body is *always* null. It's always null no matter how many times I read the message. If I go back and read the same message from PHP, the message body is populated.

Is there a set of circumstances under which libaws thinks a non-null message body is null?

[Anonymous]

Ehhhh...I see this is partly an issue with how SQS distributes messages.

That being said, is it possible that libAWS does not initialize some of its internal data structures to 0 when reading a message? I'm getting content in the message body even after an unsuccessful read attempt.

[Anonymous]

Okay, I can reproduce this error at will. It's definitely a bug in libAWS.

Also libAWS does not seem to support SQS messages > 8192 characters. There are some hard-coded limits in the parsing routines which set the maximum message body size to 8192.