Aias00 opened a new issue, #778: URL: https://github.com/apache/rocketmq-dashboard/issues/778
### Problem On the rocketmq-studio branch, the message query and trace APIs are currently backed by `MessageProviderStub` when no real message provider is configured. The backend returns `BusinessException(501, "Message query provider is not configured")`. However, `web/src/pages/instance/message.tsx` catches query and trace failures and replaces the backend message with generic UI prompts such as `消息查询失败，请稍后重试` and `消息轨迹加载失败，请稍后重试`. This makes the BASE-01 message query page look like a transient failure instead of an unavailable provider state. ### Evidence - `server/src/main/java/org/apache/rocketmq/studio/instance/message/MessageProviderStub.java` throws `BusinessException(501, "Message query provider is not configured")` for query and trace calls. - `web/src/pages/instance/message.tsx` catches errors and displays generic failure messages only. ### Expected behavior Until a real message provider is wired in, the message page should surface the backend error message as an explicit warning state for both message query and trace loading. 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 / message query and trace visibility. The proposed fix is a small UI/contract hardening change and does not implement the full message 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]
