Aias00 opened a new issue, #773: URL: https://github.com/apache/rocketmq-dashboard/issues/773
### Problem On the rocketmq-studio branch, the client connections API is currently backed by ClientProviderStub. When no real Remoting/gRPC client provider is configured, ClientProviderStub.findConnections() throws BusinessException(501, "Client connection provider is not configured"). However, web/src/pages/cluster/clients.tsx catches all failures and only shows the generic message "客户端连接加载失败，请稍后重试". This hides the actionable backend state from users and makes the CLIENT-01 page look like a transient load failure instead of an intentionally unavailable provider. ### Evidence - server/src/main/java/org/apache/rocketmq/studio/cluster/client/ClientProviderStub.java returns BusinessException(501, "Client connection provider is not configured"). - web/src/pages/cluster/clients.tsx catches errors with a generic message.error(...) and does not render an explicit unavailable state. ### Expected behavior Until a real client provider is wired in, the client connections page should surface the backend error message as an explicit warning/empty state. Users should be able to tell that the provider is not configured instead of seeing only a generic retry prompt. ### Scope This is in the RocketMQ Studio scope for CLIENT-01 / dual-protocol client connection visibility. The proposed fix is a small UI/contract hardening change and does not implement the full Remoting/gRPC 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]
