btlqql opened a new issue, #1041: URL: https://github.com/apache/rocketmq-dashboard/issues/1041
## Problem `RocketMQClientProvider.findProducerConnections(topic, producerGroup)` calls `adminExt.examineProducerConnectionInfo(producerGroup, topic)`. When the topic does not exist (or has no route), RocketMQ's admin client throws `MQClientException` (`ResponseCode.TOPIC_NOT_EXIST`), which the method converts into a `BusinessException(502, "Failed to query producer connections")`. A user querying the Clients page for a not-yet-created or already-deleted topic therefore sees a hard "query failed" error instead of an empty connection list. The 502 also conflates "the topic does not exist" with real network/authorization failures, so the UI cannot tell the two apart. ## Expected A non-existent topic is a normal "nothing here" outcome: the API returns an empty connection list, while genuine network/authorization errors still surface as 502. ## Acceptance criteria - Querying producer connections for a non-existent topic returns an empty list (HTTP 200), not 502. - Genuine failures (broker unreachable, auth) still return 502. - Unit tests cover both the TOPIC_NOT_EXIST path and the real-error path. -- 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]
