Ack the message when there's a decode error.

Previously, the message wouldn't be acked when the message
couldn't be decoded, returning early from the receive method,
before the message would be acked.

I have a suspicion that is responsible for the queue ups we saw
tonight. There were some decode errors, shortly after the logs
queue would start piling up.