You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am sure that all the content I provide is in English.
Search before asking
I had searched in the issues and found no similar issues.
Apache Dubbo Component
Java SDK (apache/dubbo)
Dubbo Version
3.2.12
Steps to reproduce this issue
Service A and B have same interface com.test.InterfaceXXX, their dubbo.application.metadata-type are same local, but group or version are different,
Consumer C only invokes com.test.InterfaceXXX of service A, the connection between C and A is allowable, but the connection between C and B is forbidden by firework.
When consumer C created dubbo reference of service A, it will get mapping metadata which mapping key is com.test.InterfaceXXX, of course the result from metadata center has both A and B
Consumer C will try to connect to both A and B to building reference of A (their metadata-type are both local), but the reference creation will always be failed because the firework will block the connection from C to B.
What you expected to happen
the mapping key should include group and version.
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!
Pre-check
Search before asking
Apache Dubbo Component
Java SDK (apache/dubbo)
Dubbo Version
3.2.12
Steps to reproduce this issue
com.test.InterfaceXXX
, theirdubbo.application.metadata-type
are samelocal
, but group or version are different,com.test.InterfaceXXX
of service A, the connection between C and A is allowable, but the connection between C and B is forbidden by firework.com.test.InterfaceXXX
, of course the result from metadata center has both A and BWhat you expected to happen
the mapping key should include group and version.
Anything else
No response
Are you willing to submit a pull request to fix on your own?
Code of Conduct
The text was updated successfully, but these errors were encountered: