IiiinSea opened a new issue, #15761: URL: https://github.com/apache/dubbo/issues/15761
### 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 3.3.4 ### Steps to reproduce this issue For example: There's a service called com.a.b.QuotaService available in both registry centers "registrySt" and "registryOnline". Now I subscribe to them in my service like this: @Reference(group = "", registry = "registrySt", interfaceClass = QuotaService.class, check = false, retries = 0, timeout = 3000) private QuotaService quotaServiceSt; @Reference(group = "", registry = "registryOnline", interfaceClass = QuotaService.class, check = false, retries = 0, timeout = 5000) private QuotaService quotaServiceOnline; During project initialization and subscription, it goes through a cache logic where the key obtained is "com.a.b.QuotaService" in both cases. This means the first one can initialize properly, but the second one reuses what's in the cache because the key is the same. <img width="1266" height="683" alt="Image" src="https://github.com/user-attachments/assets/e176e8c6-5dc8-4cb3-85b1-8b570a4b0d84"; /> <img width="1271" height="494" alt="Image" src="https://github.com/user-attachments/assets/d7cd1706-738e-431b-8772-a0852aae14d0"; /> ### What you expected to happen However, for my use case, these two References should be independent and shouldn't be reused. ### Anything else _No response_ ### Are you willing to submit a pull request to fix on your own? - [ ] 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]
