unbridled-41 opened a new issue, #5970: URL: https://github.com/apache/rocketmq-dashboard/issues/5970
### Studio Version branch: `rocketmq-studio` @ `7e7aa344` ### Describe the Bug The demo stack's directory listing describes both bundled load generators as connecting via `proxy:8080`, but they are plain clients pointed at the NameServer (`NAMESRV_ADDR`, defaulting to the NameServer address) and the compose passes `NAMESRV_ADDR: rmq-nameserver:9876` to both. Nothing in the bundled traffic exercises the proxy, so a reader looking for proxy traffic finds none. ### What Did You Expect to See? A description of what the files do. ### What Did You See Instead? A description that contradicts the code and the compose comments. ### Evidence `grep -n "NAMESRV_ADDR\|setNamesrvAddr" deploy/rocketmq/clients/*.java deploy/rocketmq/docker-compose.yml` shows the NameServer address on every client; `grep -rn "proxy\|8080" deploy/rocketmq/clients/` returns nothing. ### Impact A developer expecting proxy traffic (and a populated Proxy view) from the bundled load finds neither. ### Acceptance Criteria The listing describes the NameServer connection the clients actually use. **Corresponding PR:** #ISSUEPR# -- 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]
