[type:fix] Fix dubbo3.0 cannot get service provider information#5708
Open
hujiatai wants to merge 138 commits intoapache:masterfrom
Open
[type:fix] Fix dubbo3.0 cannot get service provider information#5708hujiatai wants to merge 138 commits intoapache:masterfrom
hujiatai wants to merge 138 commits intoapache:masterfrom
Conversation
该处解决dubbo3.0后实例服务发现时,当默认使用注册中心的地址作为元数据中心时,无法使用到默认的元数据中心获取到接口的提供者,导致rpc失败 修改此次后当没有配置元数据中心时会使用注册中心的地址作为元数据中心 2.6.1版本启用dubbo插件时没有配置元数据中心的地址配置,后续应前后端都允许元数据中心的配置
moremind
requested changes
Oct 14, 2024
...-dubbo/src/main/java/org/apache/shenyu/plugin/apache/dubbo/cache/ApacheDubboConfigCache.java
Outdated
Show resolved
Hide resolved
Member
|
pls use english, after you modify, please contact me with wechat: yijia1949 |
…sed to expose the registration, the provider of interface service cannot be obtained When solving the instance service discovery after dubbo3.0, when the default address of the registration center is used as the metadata center, the default metadata center cannot be used to obtain the interface provider, resulting in rpc failure When no metadata center is configured after this modification, the address of the registry will be used as the metadata center The address configuration of the metadata center is not configured when the dubbo plug-in is enabled in version 2.6.1, and the configuration of the metadata center should be allowed in both the front-end and back-end in the future
Fix dubbo3.0 cannot get service provider information apache#5708
Member
|
not right, you should run shenyu-integrate-combination module |
Author
|
ruined, test pass
![Uploading d4c9deab7b9fd0e35e18e6ff01fc731e.jpg…]()
|
Author
Fix dubbo application discover cannot get service provider information
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

该处解决dubbo3.0后实例服务发现时,当默认使用注册中心的地址作为元数据中心时,无法使用到默认的元数据中心获取到接口的提供者,导致rpc失败
修改此次后当没有配置元数据中心时会使用注册中心的地址作为元数据中心
2.6.1版本启用dubbo插件时没有配置元数据中心的地址配置,后续应前后端都允许元数据中心的配置
Make sure that:
./mvnw clean install -Dmaven.javadoc.skip=true.