dubbo-admin 0.5.0 tri协议 使用测试接口不成功
- Dominant language
- Go
- Stars
- 4.1k
- Forks
- 2.2k
- Avg merge
- 10d 12h
- Merged PRs (30d)
- 4
Description
rpc服务是使用dubbo3.0.12，服务使用triple协议交互
nacos-client使用2.1.1，nacos-server使用2.1.1
dubbo-admin 0.5.0
在dubbo-admin中进行接口测试的时候一直报错
"System Error, please try again later! Message:Failed to check the status of the service com.pub.chat.live.chat.userstatus.proto.LiveChatUserStatus. No provider available for the service com.pub.chat.live.chat.userstatus.proto.LiveChatUserStatus from the url consumer://192.168.1.149/com.pub.chat.live.chat.userstatus.proto.LiveChatUserStatus?application=dubbo-admin&background=false&dubbo=2.0.2&generic=true&interface=com.pub.chat.live.chat.userstatus.proto.LiveChatUserStatus&pid=1917033®ister.ip=192.168.1.149&release=3.0.8&side=consumer&sticky=false×tamp=1670641226421 to the consumer 192.168.1.149 use dubbo version 3.0.8"
但是在nacos上服务是可以看到了，而且通过nacos不通过dubbo-admin的测试接口是没有问题的
Contributor guide
Research direction
Start by reproducing the dubbo-admin interface test with Dubbo 3.0.12, dubbo-admin 0.5.0, and the Nacos 2.1.1 setup described. Compare the provider visible through Nacos with the provider lookup used by the triple-protocol test. Done means the service is discovered and the test succeeds, or the protocol/version incompatibility is documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100