stacktrace: java.lang.ClassCastException: java.util.HashMap cannot be cast to

阅读: 评论:0

stacktrace: java.lang.ClassCastException: java.util.HashMap cannot be cast to

stacktrace: java.lang.ClassCastException: java.util.HashMap cannot be cast to

今天线上发了好几封预警邮件,邮件内容如下:

看了下项目报错的代码:

        ApiResult<WithdrawResultDto> withdrawResult = loanApiService.queryWithdrawResult(contractNo);WithdrawResultDto withdraw = Data();

ApiResult 的代码:

public class ApiResult<T> implements Serializable {private static final long serialVersionUID = 1L;private boolean success;private String code;private String message;private String requestId;private T data;private ApiResult() {}}

发现逻辑上是完全没有问题的,报错是第二行代码,又看了下日志,终于发现了问题的原因:

[NettyClientWorker-thread-13{New I/O client worker #1-13}]  |-|WARN  |-|2018-12-19T16:42:37.938+08:00  |-|h.i.SerializerFactory[652]  |-|Hessian/Burla
p: &#alm.api.protoss.dto.WithdrawResultDto' is an unknown class in org.springframework.boot.loader.LaunchedURLClassLoader@507b79f7:
java.lang.ClassNotFoundException: com.mljr.malm.api.protoss.dto.WithdrawResultDto  |-|
[DubboServerHandler-10.8.104.106:24475-thread-199]  |-|INFO  |-|2018-12-19T16:42:37.940+08:00  |-|c.m.a.b.a.d.s.i.DeductionServiceImpl[268]  |-|【撤销结
算单】查询数据返回信息:{"code":"0","data":{"payUsStatus":2,"no":"18121710054227356449","withholdingRequire":1,"withdrawType":0,"lendingWay":1
,"withdrawStatus":3},"message":"成功","success":true};业务编号为18121710054227356449  |-|
[DubboServerHandler-10.8.104.106:24475-thread-199]  |-|ERROR  |-|2018-12-19T16:42:37.940+08:00  |-|c.m.a.b.a.d.f.BgisDeductionFacadeImpl[96]  |-|【结算
单撤销】系统异常,异常原因:  |-|
java.lang.ClassCastException: java.util.HashMap cannot be cast alm.api.mac.dto.apps.deduction.service.impl.DeductionServiceImpl.isCancelByTerm(DeductionServiceImpl.java:273)apps.deduction.service.impl.DeductionServiceImpl.cancelDeduction(DeductionServiceImpl.java:245)apps.deduction.biz.impl.DeductionBizImpl.cancelDeductionBill(DeductionBizImpl.java:110)apps.deduction.facade.BgisDeductionFacadeImpl.cancelDeductionBill(BgisDeductionFacadeImpl.java:88)at com.alibaba.dubbomon.bytecode.Wrapper107.invokeMethod(Wrapper107.java)at com.alibaba.dubbo.rpc.proxy.javassist.JavassistProxyFactory$1.doInvoke(JavassistProxyFactory.java:46)at com.alibaba.dubbo.rpc.proxy.AbstractProxyInvoker.invoke(AbstractProxyInvoker.java:72)at com.alibaba.dubbo.rpc.protocol.InvokerWrapper.invoke(InvokerWrapper.java:53)at com.alibaba.dubbo.rpc.filter.ExceptionFilter.invoke(ExceptionFilter.java:64)at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)at com.itor.support.MonitorFilter.invoke(MonitorFilter.java:75)at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)at com.alibaba.dubbo.rpc.filter.TimeoutFilter.invoke(TimeoutFilter.java:42)at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)at com.alibaba.dubbo.rpc.filter.AccessLogFilter.invoke(AccessLogFilter.java:154)at com.alibaba.dubbo.rpc.protocol.ProtocolFilterWrapper$1.invoke(ProtocolFilterWrapper.java:69)

前面的warning 信息指出:‘alm.api.protoss.dto.WithdrawResultDto’ is an unknown class…
后面报 ClassCastException 的却是alm.api.mac.dto.WithdrawResultDto。

看到这里,我忽然就想到了,应该是其他组的api 中涉及的dto 修改了路径,但是我们用的还是低版本的老路径,在执行下面的代码时,相当于类型的转换(从T到WithdrawResultDto):

WithdrawResultDto withdraw = Data();

因为转换的时候涉及到读取对象的全路径,全路径不一致,就报错了。

最后就是我们升级下 调用的 api 的版本,使用新路径就好了?

本文发布于:2024-02-03 04:33:52,感谢您对本站的认可!

本文链接:https://www.4u4v.net/it/170690603048674.html

版权声明:本站内容均来自互联网,仅供演示用,请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系,我们将在24小时内删除。

留言与评论(共有 0 条评论)
   
验证码:

Copyright ©2019-2022 Comsenz Inc.Powered by ©

网站地图1 网站地图2 网站地图3 网站地图4 网站地图5 网站地图6 网站地图7 网站地图8 网站地图9 网站地图10 网站地图11 网站地图12 网站地图13 网站地图14 网站地图15 网站地图16 网站地图17 网站地图18 网站地图19 网站地图20 网站地图21 网站地图22/a> 网站地图23