RockteMQ-AI commented on issue #1243: URL: https://github.com/apache/rocketmq-dashboard/issues/1243#issuecomment-5215147049
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified against the current codebase on the `rocketmq-studio` branch. **Root Cause:** `RocketMQBrokerConfigService.namesrvAddr()` (line 118-123) reads from `RocketMQProperties` which is bound to the global `studio.rocketmq.namesrv-addr` config. Both `getBrokerConfig()` and `updateBrokerConfig()` route through this global endpoint regardless of which instance the user selected in the UI. **Impact:** In a multi-instance Studio deployment, Broker configuration reads/writes can target the wrong RocketMQ cluster. This is a data-safety risk — a user intending to configure Cluster A could silently modify Cluster B. **Severity:** high **Affected files:** - `RocketMQBrokerConfigService.java:43,59` — both operations use `namesrvAddr()` - `ClusterService.java:78` — enrichment path also affected 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]
