For example, let's say you have a message and its default message visibility timeout
is 30 minutes. You could call
ChangeMessageVisiblity with a value of
two hours and the effective timeout would be two hours and 30 minutes. When that time
comes near you could again extend the time out by calling ChangeMessageVisiblity,
but this time the maximum allowed timeout would be 9 hours and 30 minutes.
There is a 120,000 limit for the number of inflight messages per queue. Messages are inflight after they have been received from the queue by a consuming component, but have not yet been deleted from the queue. If you reach the 120,000 limit, you will receive an OverLimit error message from Amazon SQS. To help avoid reaching the limit, you should delete the messages from the queue after they have been processed. You can also increase the number of queues you use to process the messages.
VisibilityTimeoutto an amount more than the maximum time left, Amazon SQS returns an error. It will not automatically recalculate and increase the timeout to the maximum time remaining.
Version: (assembly version)
public virtual ChangeMessageVisibilityResponse ChangeMessageVisibility( String queueUrl, String receiptHandle, Int32 visibilityTimeout )
The URL of the Amazon SQS queue to take action on.
The receipt handle associated with the message whose visibility timeout should be changed. This parameter is returned by the ReceiveMessage action.
The new value (in seconds - from 0 to 43200 - maximum 12 hours) for the message's visibility timeout.
Supported in: 4.5, 4.0, 3.5