Deleting SQS Message with Receipt Handle

Question

I am currently using amazon's SQS, and am having issues when trying to delete queue messages that are currently "In Flight".

Below is some example code:

ReceiveMessageRequest queueRequest = new ReceiveMessageRequest();
        queueRequest.WithMaxNumberOfMessages(1);
        queueRequest.WithQueueUrl(config.QueueURL);
        queueRequest.WithAttributeName("All");

        ReceiveMessageResponse response = sqs.ReceiveMessage(queueRequest);

        if (response.IsSetReceiveMessageResult())
        {
            ReceiveMessageResult result = response.ReceiveMessageResult;

            if (result.IsSetMessage())
            {
                if (result.Message.First() != null)
                {
                    return new Tuple<string, string, bool>(result.Message.First().ReceiptHandle, result.Message.First().Body ?? null, false);
                }
            }
        }

Now after receiving both the Handle, and the message body, I store the Receipt handle string into cloud storage (DynamoDB for example). I then later on load that handle out of the storage service, and call a delete with something similar to the following:

sqs.DeleteMessage(new DeleteMessageRequest() { QueueUrl = "urL", ReceiptHandle = handle });

However, when running that line, I receive a "The input receipt handle is invalid" error message.

Note, I know that this message has not gotten re-received, so the receipt handle being logged, should be the most recent one. Also note that I can currently delete messages within that same application, simply by sleeping after the message is received, and then trying to delete it as above!

Any ideas?

Did you resolve this Samuel ? I appear to be running into the same issue. — Jason Hyland, Apr 12 '14 at 14:51

b-s-d · Answer 1 · 2015-04-01T18:08:15.930

3

Make sure you are using the exact same URL that references the queue when you are executing both operations (ReceiveMessage and DeleteMessage).

edited Apr 01 '15 at 18:08

answered Apr 01 '15 at 17:26

b-s-d

4,953
2
25
31

score 2 · Answer 2 · answered Oct 05 '12 at 08:52

2

You have to wait until a message's VisibilityTimeout has expired before you can act on it again. This allows the machine handling that message the time to do whatever it needs to do.

answered Oct 05 '12 at 08:52

Ryan Parman

6,855
1
29
43

1

So let's say a Machine A is handing a message X. Machine A sets the visibility timeout to 2 days from now. And then it starts to operate on this message (delete it). Would that work? – Ravindranath Akila Jun 08 '15 at 10:58

score 0 · Answer 3 · answered May 10 '15 at 14:21

0

The ReceiptHandle contains some special characters, which are sensitive to URL. So You need to first URL encode it. I did the same and it worked.

answered May 10 '15 at 14:21

Hari Das

10,145
7
62
59

Deleting SQS Message with Receipt Handle

3 Answers3