请稍等 ...
×

采纳答案成功!

向帮助你的同学说点啥吧!感谢那些助人为乐的人

ImRouterProviderApplication启动报错

org.apache.dubbo.remoting.RemotingException: client(url: dubbo://192.168.1.3:9099/org.qiyu.live.im.core.server.interfaces.rpc.IRouterHandlerRpc?anyhost=true&application=qiyu-live-im-router-provider&background=false&category=providers,configurators,routers&cluster=imRouter&codec=dubbo&deprecated=false&dubbo=2.0.2&dynamic=true&executor-management

org.apache.dubbo.rpc.RpcException: Fail to create remoting client for service(dubbo://192.168.1.3:9099/org.qiyu.live.im.core.server.interfaces.rpc.IRouterHandlerRpc?anyhost=true&application=qiyu-live-im-router-provider&background=false&category=providers,configurators,routers&cluster=imRouter&codec=dubbo&deprecated=false&dubbo=2.0.2&dynamic=true&executor-management-mode=default&file.cache=true&generic=false&heartbeat=60000&interface=org.qiyu.live.im.core.server.interfaces.rpc.IRouterHandlerRpc&methods=sendMsg&path=org.qiyu.live.im.core.server.interfaces.rpc.IRouterHandlerRpc&pid=28192&prefer.serialization=fastjson2,hessian2&protocol=dubbo&qos.enable=false&release=3.2.0-beta.3&service-name-mapping=true&side=consumer&sticky=false&timestamp=1715342518814&unloadClusterRelated=false): client(url: dubbo://192.168.1.3:9099/org.qiyu.live.im.core.server.interfaces.rpc.IRouterHandlerRpc?anyhost=true&application=qiyu-live-im-router-provider&background=false&category=providers,configurators,routers&cluster=imRouter&codec=dubbo&deprecated=false&dubbo=2.0.2&dynamic=true&executor-management-mode=default&file.cache=true&generic=false&heartbeat=60000&interface=org.qiyu.live.im.core.server.interfaces.rpc.IRouterHandlerRpc&methods=sendMsg&path=org.qiyu.live.im.core.server.interfaces.rpc.IRouterHandlerRpc&pid=28192&prefer.serialization=fastjson2,hessian2&protocol=dubbo&qos.enable=false&release=3.2.0-beta.3&service-name-mapping=true&side=consumer&sticky=false&timestamp=1715342518814&unloadClusterRelated=false) failed to connect to server /192.168.1.3:9099 client-side timeout 3000ms (elapsed: 3013ms) from netty client 192.168.3.9 using dubbo version 3.2.0-beta.3
at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.initClient(DubboProtocol.java:613) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.buildReferenceCountExchangeClient(DubboProtocol.java:575) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.buildReferenceCountExchangeClientList(DubboProtocol.java:562) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.getSharedClient(DubboProtocol.java:495) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.getClients(DubboProtocol.java:429) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.protocolBindingRefer(DubboProtocol.java:410) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol.refer(DubboProtocol.java:401) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.qos.protocol.QosProtocolWrapper.refer(QosProtocolWrapper.java:85) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.rpc.protocol.ProtocolListenerWrapper.refer(ProtocolListenerWrapper.java:77) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.rpc.cluster.filter.ProtocolFilterWrapper.refer(ProtocolFilterWrapper.java:74) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.rpc.protocol.ProtocolSerializationWrapper.refer(ProtocolSerializationWrapper.java:52) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.rpc.ProtocolAdaptive.refer(ProtocolAdaptive.refer(ProtocolAdaptive.refer(ProtocolAdaptive.java) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.registry.integration.RegistryDirectory.toInvokers(RegistryDirectory.java:399) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.registry.integration.RegistryDirectory.refreshInvoker(RegistryDirectory.java:261) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.registry.integration.RegistryDirectory.refreshOverrideAndInvoker(RegistryDirectory.java:202) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.registry.integration.RegistryDirectory.notify(RegistryDirectory.java:180) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.registry.support.AbstractRegistry.notify(AbstractRegistry.java:533) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.registry.support.FailbackRegistry.doNotify(FailbackRegistry.java:373) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.registry.support.FailbackRegistry.notify(FailbackRegistry.java:365) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.registry.nacos.NacosRegistry.notifySubscriber(NacosRegistry.java:615) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3]
at org.apache.dubbo.registry.nacos.NacosRegistry.doSubscribe(NacosRegistry.java:231) ~[dubbo-3.2.0-beta.3.jar:3.2.0-beta.3] 老师麻烦你看我下 这个问题是什么原因呢

正在回答 回答被采纳积分+3

1回答

Danny_Idea 2024-05-13 07:52:36
router的dubbo服务是不是没有部署起来
0 回复 有任何疑惑可以回复我~
  • 提问者 如此深情 #1
    老师,这个确实没有部署。那我在本地启动的话 应该怎么修改
    回复 有任何疑惑可以回复我~ 2024-05-15 20:47:21
  • Danny_Idea 回复 提问者 如此深情 #2
    把router服务部署起来 作为dubbo的服务提供者 再试试
    回复 有任何疑惑可以回复我~ 2024-05-15 20:54:57
  • 提问者 如此深情 回复 Danny_Idea #3
    回复 Danny_Idea:老师有没有办法不部署,只在本地调式启动呢。要是有办法的话 应该怎么修改
    回复 有任何疑惑可以回复我~ 2024-05-15 21:54:03
问题已解决,确定采纳
还有疑问,暂不采纳
意见反馈 帮助中心 APP下载
官方微信