ufwq comments

Results 10 comments of


                                            ufwq

No provider available from registry 192.168.1.169:8848 for service com.flybycloud.microapp.biz.flyby.business.spec.CloudPushDataBusiness on consumer 192.168.1.169 use dubbo version 2.7.8, please check status of providers(disabled, not registered or in blacklist).

spring cloud Hoxton.SR8 spring cloud alibaba 2.2.6-bugfix4-SNAPSHOT spring boot 2.3.8.RELEASE dubbo 2.7.8 用这个版本吗

No provider available from registry 192.168.1.169:8848 for service com.flybycloud.microapp.biz.flyby.business.spec.CloudPushDataBusiness on consumer 192.168.1.169 use dubbo version 2.7.8, please check status of providers(disabled, not registered or in blacklist).

hi，2.2.6正式版准备发布了没

No provider available from registry 192.168.1.169:8848 for service com.flybycloud.microapp.biz.flyby.business.spec.CloudPushDataBusiness on consumer 192.168.1.169 use dubbo version 2.7.8, please check status of providers(disabled, not registered or in blacklist).

2.2.6.RC1版本测试，dubbo服务提供者断开后，消费者会抛这个异常，但是之前的找不到服务问题没有再出现，继续测试 2021-07-09 11:46:25.407 WARN 7752 --- [ncesChangeEvent] o.a.d.r.p.d.LazyConnectExchangeClient : safe guard client , should not be called ,must have a bug. java.lang.IllegalStateException: safe guard client , should not be called...

No provider available from registry 192.168.1.169:8848 for service com.flybycloud.microapp.biz.flyby.business.spec.CloudPushDataBusiness on consumer 192.168.1.169 use dubbo version 2.7.8, please check status of providers(disabled, not registered or in blacklist).

rc1版本是好的，release版本问题再次出现

No provider available from registry 192.168.1.169:8848 for service com.flybycloud.microapp.biz.flyby.business.spec.CloudPushDataBusiness on consumer 192.168.1.169 use dubbo version 2.7.8, please check status of providers(disabled, not registered or in blacklist).

spring cloud Hoxton.SR9 spring cloud alibaba 2.2.6-RC1 spring boot 2.3.2.RELEASE dubbo 2.7.8 rc1版本再次出现问题

No provider available from registry 192.168.1.169:8848 for service com.flybycloud.microapp.biz.flyby.business.spec.CloudPushDataBusiness on consumer 192.168.1.169 use dubbo version 2.7.8, please check status of providers(disabled, not registered or in blacklist).

@theonefx spring cloud Hoxton.SR8 spring cloud alibaba 2.2.6.RELEASE spring boot 2.3.2.RELEASE dubbo 2.7.8 在本机测试，没有问题。通过docker 部署到ecs服务器, 采用 docker run -tid --net=host xxx的方式，经常找不到服务

No provider available from registry 192.168.1.169:8848 for service com.flybycloud.microapp.biz.flyby.business.spec.CloudPushDataBusiness on consumer 192.168.1.169 use dubbo version 2.7.8, please check status of providers(disabled, not registered or in blacklist).

服务消费者是正常启动的，就是更新服务提供者之后，消费者偶发性找不到服务提供者

No provider available from registry 192.168.1.169:8848 for service com.flybycloud.microapp.biz.flyby.business.spec.CloudPushDataBusiness on consumer 192.168.1.169 use dubbo version 2.7.8, please check status of providers(disabled, not registered or in blacklist).

> 你们是不是在调试时几个相互订阅服务**同时启动**、或者是几个服务并行注册上线到nacos？ > > 根据我调试结果得出、几个服务在同时启动时、先启动好的上游服务注册入nacos之后、发生服务变更事件、但nacos并不会通知**正在注册中**的下游服务服务变更事件、从而导致下游服务没有获取到最新的订阅服务信息从而导致 > No provider available from registr 错误、如果每个服务顺序、不并行启动是不会有此问题的。 > > 为了避免在注册中途有订阅服务注册上nacos却没有通知到本服务、故此我在服务启动之后会主动去发起一次订阅服务更新事件、经过测试之后已经解决此问题。 > > 环境： > spring-cloud-alibaba 2.2.6.RELEASE > nacos-service 2.0.3 > > 解决方法：服务启动后主动发起服务变更事件进行补偿。 > >...

No provider available from registry 192.168.1.169:8848 for service com.flybycloud.microapp.biz.flyby.business.spec.CloudPushDataBusiness on consumer 192.168.1.169 use dubbo version 2.7.8, please check status of providers(disabled, not registered or in blacklist).

> > > 你们是不是在调试时几个相互订阅服务**同时启动**、或者是几个服务并行注册上线到nacos？ > > > 根据我调试结果得出、几个服务在同时启动时、先启动好的上游服务注册入nacos之后、发生服务变更事件、但nacos并不会通知**正在注册中**的下游服务服务变更事件、从而导致下游服务没有获取到最新的订阅服务信息从而导致 > > > No provider available from registr 错误、如果每个服务顺序、不并行启动是不会有此问题的。 > > > 为了避免在注册中途有订阅服务注册上nacos却没有通知到本服务、故此我在服务启动之后会主动去发起一次订阅服务更新事件、经过测试之后已经解决此问题。 > > > 环境： > > > spring-cloud-alibaba...