RockteMQ-AI commented on issue #2635: URL: https://github.com/apache/rocketmq-dashboard/issues/2635#issuecomment-5437480499
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** In `RocketMQDLQProvider`, the "selected resend" path (by msgIds) first calls `collectDeadLetters` with a hardcoded 7-day window (`end - 7 * 24 * ONE_HOUR_MILLIS`, line 258) and `RESEND_HARD_CAP = 5000` (line 77). Messages that fall outside this 7-day window, or are beyond the 5000-message cap, are silently excluded from the scan — so user-selected message IDs that exist in the DLQ but outside the scan range are never found and never resent. **Impact:** Users select specific DLQ messages for resend via the UI, but some are silently dropped because the backend scan window is too narrow. No error is reported — the user sees a lower-than-expected resend count with no explanation. **Severity:** Medium — data loss risk for DLQ operations outside the fixed window. **Fix direction:** Either (a) accept the msgIds directly and look them up by offset/ID without the time-window scan, or (b) expand the scan window dynamically based on the selected messages' timestamps, or (c) surface a clear warning when the scan window may have missed messages. An automated fix proposal can 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]
