Skip to content

[ISSUE #402] Add proxy fallback for request codes 106/206 not supported#417

Closed
itxaiohanglover wants to merge 1 commit into
apache:masterfrom
itxaiohanglover:fix/request-type-not-supported-proxy
Closed

[ISSUE #402] Add proxy fallback for request codes 106/206 not supported#417
itxaiohanglover wants to merge 1 commit into
apache:masterfrom
itxaiohanglover:fix/request-type-not-supported-proxy

Conversation

@itxaiohanglover

Copy link
Copy Markdown

Fixes #402. When dashboard connects to RocketMQ 5.4.0+ in proxy mode, request codes 106 (GET_BROKER_CLUSTER_INFO) and 206 (GET_ALL_TOPIC_LIST_FROM_NAMESERVER) are not supported by the broker. Added proxy fallback in ClusterServiceImpl, ClusterInfoService, and TopicServiceImpl.

…upported

When RocketMQ Dashboard connects to RocketMQ 5.4.0+ in proxy mode,
certain request codes (106 GET_BROKER_CLUSTER_INFO, 206
GET_ALL_TOPIC_LIST_FROM_NAMESERVER) are not supported by the broker.

Add getBrokerClusterInfo and getAllTopicListFromNameServer methods to
ProxyAdmin/ProxyAdminImpl that send requests to the proxy address.
Update ClusterServiceImpl, ClusterInfoService, and TopicServiceImpl
to fall back to the proxy when the standard mqAdminExt methods fail.
@itxaiohanglover

Copy link
Copy Markdown
Author

Closing in favor of #418 which provides a more comprehensive fix covering both #402 and #381 with proxy fallback for request codes 106, 206, and 208.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

request type 106/206 not supported

1 participant