RockteMQ-AI commented on issue #4601: URL: https://github.com/apache/rocketmq-dashboard/issues/4601#issuecomment-5749415750
**Issue Evaluation** Category: `bug` | Status: **Confirmed** Thank you for the detailed report. The issue has been verified against the codebase. **Root Cause:** `RocketMQMessageProvider.consumeMessageDirectly` does not grade the broker's "not online" response. The `MQClientException` with `ResponseCode.SYSTEM_ERROR` and remark containing "not online" propagates uncaught to `MqAdminExtFactory`, which wraps it as a generic 502 — while the sibling endpoint `RocketMQConsumerDiagnosticsProvider` already maps the identical broker response to a 404. **Impact:** Operators see an opaque 502 gateway failure instead of a clear "client not online" business state. Monitoring systems that classify 5xx are also affected. **Severity:** Medium — incorrect error grading, no data loss. **Assessment:** The fix is straightforward: add exception grading in `consumeMessageDirectly` to map "not online" to a 404 `BusinessException`, consistent with the existing `RocketMQConsumerDiagnosticsProvider#diagnosticsFailure` pattern. A fix PR is welcome. --- *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]
