pilichoumao opened a new issue, #6018: URL: https://github.com/apache/rocketmq-dashboard/issues/6018
A consumer connected through a Proxy can be reported as not found when the Proxy running-info query fails. On `rocketmq-studio@7e7aa344`, `ProxyConsumerResolver.resolveConsumerRunningInfo` catches query exceptions and returns null. `RocketMQConsumerDiagnosticsProvider` then falls back to the Broker. A Proxy-connected consumer is normally absent from the Broker, whose `CONSUMER_NOT_ONLINE` reply becomes a 404. The failed Proxy query is lost. The console also uses the capture-unsupported notice for rejected stack requests. Deterministic reproduction: discover one Proxy; have its running-info request throw a timeout-shaped exception; have the Broker reply `CONSUMER_NOT_ONLINE`; call `getConsumerStack` for the same instance/group/client. A regression asserting a query failure (502) fails with actual 404 on that commit. Expected: retain failed-query coverage when no endpoint produces diagnostics; still allow a successful Broker fallback for direct consumers. Only explicit absence should be reported as not found. The console should distinguish query failure from a successful response without a stack. I have prepared a focused fix and regression coverage using the existing Resolver and Admin pool. No new Proxy client, endpoint, dependency or configuration is needed. This concerns running-info/stack diagnostics, not the connection inventories being changed by #5958 and #5960. -- 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]
