yuluo-yx opened a new issue, #2915: URL: https://github.com/apache/rocketmq-dashboard/issues/2915
BrokerConfigDiffService catches broker read failures and marks the broker unreachable, but it drops the BusinessException message. The response model and cluster page both provide a message field, so operators only see Unreadable and cannot tell whether the cause was timeout, authentication, or another broker error. Reproduction: 1. Compare a cluster where one broker config read throws BusinessException with a diagnostic message. 2. Inspect the failed broker entry in the response. Actual: message is null. Expected: retain the broker read failure message in the corresponding status entry. -- 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]
