問題文
Messages appear in the dead-letter queue with the reason indicating that the maximum delivery count was exceeded, and the consumer's logs show lock-lost and receiver-closed errors when completing messages. According to the documentation's troubleshooting table, what does this combination point to?
選択肢
- The message body exceeds the size quota, so the settlement call is rejected and the delivery count keeps climbing until the limit is reached
- The message lacks a session identifier, so the receiver cannot acquire a lock on it and settlement never succeeds
- The message time to live expired while it was still being processed, which invalidates the lock held by the consumer and produces the lock-lost errors seen in the logs
- Settlement is not reaching the service before the lock is lost, so the message is redelivered repeatedly even though processing may have succeeded