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
dubbo3.3.2,jdk17,springboot3.4.1,nacos2.4
Steps to reproduce this issue
[DUBBO] Can't find an instance URL using the default preferredProtocol "dubbo", falling back to the strategy that pick the first found protocol. Please try modifying the config of dubbo.application.protocol, dubbo version: 3.3.2, current host: 172.16.18.119, error code: 4-2. This may be caused by typo in preferred protocol, go to https://dubbo.apache.org/faq/4/2 to find instructions.
一直有这个警告,按照提示修改序列化方式以后还是不行,相关的依赖已经加上了
What you expected to happen
希望能解决
Anything else
能尽快解决
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!
Thanks, but the demo you provided for the quick start is also configured like this, there is no description of dubbo.application.protocol, only dubbo.protocol, but if I put dubbo.protocol=dubbo, there is no problem with this problem
Pre-check
Search before asking
Apache Dubbo Component
Java SDK (apache/dubbo)
Dubbo Version
dubbo3.3.2,jdk17,springboot3.4.1,nacos2.4
Steps to reproduce this issue
[DUBBO] Can't find an instance URL using the default preferredProtocol "dubbo", falling back to the strategy that pick the first found protocol. Please try modifying the config of dubbo.application.protocol, dubbo version: 3.3.2, current host: 172.16.18.119, error code: 4-2. This may be caused by typo in preferred protocol, go to https://dubbo.apache.org/faq/4/2 to find instructions.
一直有这个警告,按照提示修改序列化方式以后还是不行,相关的依赖已经加上了
What you expected to happen
希望能解决
Anything else
能尽快解决
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: