RockteMQ-AI commented on issue #1413: URL: https://github.com/apache/rocketmq-clients/issues/1413#issuecomment-6294014289
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** The delivery_attempt counter bug has been verified. The local retry loop increments `num_retries` but never writes it back to the `MessageView`, so the listener always sees `delivery_attempt = 1`. This breaks retry logic that depends on attempt count, DLQ reporting, and retry delay calculation. **Root Cause:** In `PushConsumerImpl::process_message`, the retry loop increments `num_retries` but does not update `message.delivery_attempt` before re-calling the listener. **Impact:** Retry attempt count is always 1; DLQ reports wrong attempt count; retry delay calculation uses wrong attempt; retry logging is misleading. **Severity:** Medium (functional correctness issue) An automated fix proposal will be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by RockteMQ-AI* -- 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]
