Aias00 opened a new issue, #1651: URL: https://github.com/apache/rocketmq-dashboard/issues/1651
## Problem `RocketMQDLQProvider.resendMessages()` treats a failed dead-letter scan as an empty scan. `collectDeadLetters()` catches both queue-level errors and the top-level consumer/start/fetch errors, logs them, and returns an empty `List<MessageExt>`. The caller then records and returns `NO_MESSAGES`. This makes a remote failure indistinguishable from a successful scan that found no messages, so an operator can incorrectly conclude that a DLQ is empty. ## Current behavior - per-queue scan errors are swallowed at `RocketMQDLQProvider.collectDeadLetters()`; - a failed consumer start or queue discovery is swallowed too; - `resendMessages()` maps the resulting empty list to `NO_MESSAGES`. ## Expected behavior - an all-failed scan returns a structured 502 error instead of `NO_MESSAGES`; - a partially failed scan preserves resend results but exposes that the scan is incomplete; - audit records distinguish successful empty scans from scan failures; - add regression coverage for both all-failed and partial-failure paths. ## Scope Track 1 / DLQ runtime diagnostics. This does not change normal pull-offset handling or resend transport semantics. -- 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]
