Aias00 opened a new issue, #686: URL: https://github.com/apache/rocketmq-dashboard/issues/686
## Problem The Studio backend currently wires `DLQProviderStub` as a production Spring component. It returns fixed sample DLQ groups and accepts resend requests as a no-op. Evidence: - `server/src/main/java/org/apache/rocketmq/studio/instance/dlq/DLQProviderStub.java` contains hard-coded DLQ groups. - `DLQProviderStub.resendMessages` only logs and returns without resending messages. ## Impact This is in the Track 1 / BASE-01 scope. DLQ listing and resend are baseline dashboard operations. Returning sample DLQ data and successful no-op resend responses can mislead operators. ## Expected Until a real DLQ provider is connected, the API should fail explicitly with a structured unsupported/not-implemented response, or route to a real provider when available. -- 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]
