cause: Fail to decode request due to: RpcInvocation [How to Solve]

Stack:

com.alibaba.dubbo.rpc.RpcException: Failed to invoke the method getRefundDetail in the service com.raycloud.zdtrade.api.IRefundService. Tried 6 times of the providers [39.100.56.187:31000] (1/1) from the registry ali-zk.superboss.cc:2181 on the consumer 172.16.30.53 using the dubbo version 2.6.2. Last error is: Failed to invoke remote method: getRefundDetail, provider: dubbo://39.100.56.187:31000/com.raycloud.zdtrade.api.IRefundService?anyhost=false&application=zd-marketing-schedule-dev&check=false&default.check=false&default.init=false&default.retries=0&default.timeout=60000&dubbo=2.6.0&generic=false&interface=com.raycloud.zdtrade.api.IRefundService&logger=slf4j&methods=getRefundDetail&pid=50045&pln=zd-dubbo-gateway&register.ip=172.16.30.53&remote.timestamp=1629730138908&retries=5&revision=1.0.1-20210820.055213-8&serialization=hessian2&side=consumer&timeout=4000&timestamp=1629773331155&version=1.0.0-dev-out, cause: Fail to decode request due to: RpcInvocation [methodName=getRefundDetail, parameterTypes=[class com.raycloud.zdtrade.api.request.RefundRequest], arguments=null, attachments={path=com.raycloud.zdtrade.api.IRefundService, input=458, dubbo=2.6.2, version=1.0.0-dev-out}]

Solution:
Upgrade of jar package from 1.0.0 to 1.0.1 causes.

Checking ideas: 
1. whether to pass parameters to achieve Serializable
2. whether the jar package version is the same on both sides
3. whether the dubbo service version is correct

Similar Posts: