Aias00 opened a new issue, #780: URL: https://github.com/apache/rocketmq-dashboard/issues/780
### Problem On the rocketmq-studio branch, the DLQ list and resend APIs are currently backed by `DLQProviderStub` when no real DLQ provider is configured. The backend returns `BusinessException(501, "DLQ provider is not configured")`. However, `web/src/pages/instance/dlq.tsx` catches list and resend failures and replaces the backend message with generic UI prompts such as `死信队列加载失败，请稍后重试` and `提交重投任务失败，请稍后重试`. This makes the BASE-01 DLQ page look like a transient failure instead of an unavailable provider state. ### Evidence - `server/src/main/java/org/apache/rocketmq/studio/instance/dlq/DLQProviderStub.java` throws `BusinessException(501, "DLQ provider is not configured")` for list and resend calls. - `web/src/pages/instance/dlq.tsx` catches errors and displays generic failure messages only. ### Expected behavior Until a real DLQ provider is wired in, the DLQ page should surface the backend error message as an explicit warning state for list loading and resend submission. Users should be able to distinguish an unconfigured provider from a temporary retryable failure. ### Scope This is in the RocketMQ Studio scope for BASE-01 / DLQ management. The proposed fix is a small UI/contract hardening change and does not implement the full DLQ provider. -- 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]
