dslztx opened a new issue, #16381: URL: https://github.com/apache/dubbo/issues/16381
### Pre-check - [x] I am sure that all the content I provide is in English. ### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar issues. ### Apache Dubbo Component Java SDK (apache/dubbo) ### Dubbo Version Dubbo 3.3.6，openjdk 21 ### Steps to reproduce this issue if the dubbo consumer xml config is as follow ``` <dubbo:registry` id="zk1" protocol="zookeeper" address="${ZK1_ADDRESS:10.47.181.23:2181,10.47.181.24:2181,10.47.181.25:2181}"/> <dubbo:registry id="zk2" protocol="zookeeper" address="${ZK2_ADDRESS:10.47.181.20:2181,10.47.181.21:2181,10.47.181.22:2181}"/> <dubbo:reference id="app1" interface="com.test.app1" registry="zk1"/> <dubbo:reference id="app2" interface="com.test.app2" registry="zk2"/> ``` in which ZK1_ADDRESS and ZK2_ADDRESS are env variables. what is exactly needed is that ZK1_ADDRESS and ZK2_ADDRESS may be the same or different. when ZK1_ADDRESS and ZK2_ADDRESS are the same, current implementation will only register zk1 registy config successfully, the zk2 registry config is identified as duplication，then it throws exception `java.lang.IllegalStateException: Registry not found: zk2` when loading app2 reference config ### What you expected to happen zk1 and zk2 are all registered successfully. ### Anything else _No response_ ### Do you have a (mini) reproduction demo? - [ ] Yes, I have a minimal reproduction demo to help resolve this issue more effectively! ### Are you willing to submit a pull request to fix on your own? - [x] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
