RockteMQ-AI commented on issue #10945: URL: https://github.com/apache/rocketmq/issues/10945#issuecomment-5394925338
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The analysis correctly identifies that `PopReviveService` uses the wrong `PopCheckPoint` when recoding batch messages. When a multi-message batch is pulled for retry, the reviving logic applies the checkpoint of the last message in the batch to all messages, rather than matching each message to its own checkpoint. **Root Cause:** Index mismatch in batch retry recoding — the checkpoint lookup does not account for per-message offsets within a batch. **Impact:** Retry messages may be delivered with incorrect delivery count or metadata, potentially causing premature DLQ routing or duplicate processing. **Severity:** Medium The proposed fix scope (correct per-message checkpoint lookup in batch retry path + regression test) is appropriate. --- *Automated evaluation by github-manager* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
