Tried 3 times of the providers [192.168.1:20881] (1/1) from the registry 192.168.25.128:2181 问题解决

本文解析了客户端请求Dubbo服务出现三次失败的原因,并提供了解决方案,即通过设置服务调用的超时时间来避免服务立即过期的问题。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

出现这个问题,说明客户端请求结果3次失败,其中一个原因是:dubbo服务的过期时间,如果是debug调试运行,那么默认过期时间是立即过期,这时候要加上timeout,例如:<dubbo:service interface="com.taotao.content.service.ContentService" ref="contentServiceImpl" timeout="300000" />。这时候把过期时间设置成300秒,问题即可解决!

Failed to invoke the method sendMessage in the service com.itbz.shopping_common.service.MessageService. Tried 3 times of the providers [192.168.66.10:20880] (1/1) from the registry 192.168.66.159:2181 on the consumer 192.168.119.1 using the dubbo version 2.7.8. Last error is: Invoke remote method timeout. method: sendMessage, provider: dubbo://192.168.66.10:20880/com.itbz.shopping_common.service.MessageService?anyhost=true&application=shopping_user_customer_api&check=false&deprecated=false&dubbo=2.0.2&dynamic=true&generic=false&init=false&interface=com.itbz.shopping_common.service.MessageService&metadata-type=remote&methods=sendMessage&pid=2912&qos.enable=false&register.ip=192.168.119.1&release=2.7.8&remote.application=shopping_message_service&side=consumer&sticky=false&timestamp=1689070199503, cause: org.apache.dubbo.remoting.TimeoutException: Waiting server-side response timeout by scan timer. start time: 2023-07-11 18:12:40.651, end time: 2023-07-11 18:12:41.662, client elapsed: 1 ms, server elapsed: 1010 ms, timeout: 1000 ms, request: Request [id=2, version=2.0.2, twoway=true, event=false, broken=false, data=RpcInvocation [methodName=sendMessage, parameterTypes=[class java.lang.String, class java.lang.String], arguments=[185909224615, 9527], attachments={path=com.itbz.shopping_common.service.MessageService, remote.application=shopping_user_customer_api, interface=com.itbz.shopping_common.service.MessageService, version=0.0.0}]], channel: /192.168.66.10:63073 -> /192.168.66.10:20880
07-12
Failed to invoke the method selectOptStepVOList in the service com.sdtjla.risk.api.RemoteRiskLibraryService. Tried 1 times of the providers [192.168.137.74:20881] (1/1) from the registry 127.0.0.1:8848 on the consumer 192.168.137.74 using the dubbo version 3.2.14. Last error is: Failed to invoke remote method: selectOptStepVOList, provider: DefaultServiceInstance{serviceName=&#39;aqsc-risk&#39;, host=&#39;192.168.137.74&#39;, port=20881, enabled=true, healthy=true, metadata={dubbo.endpoints=[{"port":20881,"protocol":"dubbo"}], dubbo.metadata.revision=c03cee6db2f2d2895ea5450b77ad5d3a, dubbo.metadata.storage-type=remote, timestamp=1750323797617}}, service{name=&#39;com.sdtjla.risk.api.RemoteRiskLibraryService&#39;,group=&#39;null&#39;,version=&#39;null&#39;,protocol=&#39;dubbo&#39;,port=&#39;20881&#39;,params={check.serializable=false, side=provider, release=3.2.14, methods=selectCtrlMeasureVOList,selectOptStepVOList,selectVOById, logger=slf4j, deprecated=false, dubbo=2.0.2, interface=com.sdtjla.risk.api.RemoteRiskLibraryService, service-name-mapping=true, generic=false, serialize.check.status=DISABLE, metadata-type=remote, application=aqsc-risk, prefer.serialization=fastjson2,hessian2, dynamic=true, REGISTRY_CLUSTER=default:dev},}, cause: Failed to send message Request [id=3145409504665833018, version=2.0.2, twoWay=true, event=false, broken=false, mPayload=0, data=null] to /192.168.137.74:20881, cause: failed to access class java.util.zip.ZipFile$CleanableResource from class com.alibaba.fastjson2.writer.OWG_38_15_JarFile (java.util.zip.ZipFile$CleanableResource is in module java.base of loader &#39;bootstrap&#39;; com.alibaba.fastjson2.writer.OWG_38_15_JarFile is in unnamed module of loader com.alibaba.fastjson2.util.DynamicClassLoader @6f8fa189) 怎么解决
最新发布
06-20
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值