RockteMQ-AI commented on issue #3359: URL: https://github.com/apache/rocketmq-dashboard/issues/3359#issuecomment-5552336559
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** `TopicController.getTopicRoutes` (line 85) and `getTopicConsumers` (line 92) call `metadataService.getTopicRoutes()` / `getTopicConsumers()` without handling the case where the topic exists in the metadata DB but has no live broker route. The metadata service propagates the broker lookup failure as an unhandled exception, which surfaces as a 502 to the frontend. **Impact:** Topic detail modal shows a generic error for orphaned topics. The sync flow silently filters out these failures, so the missing-route report is incomplete. **Severity:** medium (degraded UX for edge-case topics; sync report accuracy affected) **Verification:** Code confirms both endpoints lack exception handling for missing routes. The sync flow in `MetadataService` catches per-topic failures but filters them out, hiding the root cause from users. An automated fix proposal can be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by RockteMQ-AI* -- 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]
