一次异常排查 java.lang.reflect.MalformedParameterizedTypeException

84 阅读 0 评论 56 点赞

我是靠谱客的博主专一篮球，最近开发中收集的这篇文章主要介绍一次异常排查 java.lang.reflect.MalformedParameterizedTypeException，觉得挺不错的，现在分享给大家，希望可以做个参考。

概述

一次异常排查 java.lang.reflect.MalformedParameterizedTypeException

先说结论,这种问题基本上都是引入了冲突的jar包导致,排查需要从是否存在冲突jar包入手

可能是引入的开源jar包冲突.
也可能是自身内部工程的jar包冲突导致.

目前在网络上搜到的基本都是,spring ,ibatits 框架版本的问题导致的,如果没有,就需要检查是否有其他的冲突.

异常报错

java.lang.reflect.MalformedParameterizedTypeException
	at sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl.validateConstructorArguments(ParameterizedTypeImpl.java:60)
	at sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl.<init>(ParameterizedTypeImpl.java:53)
	at sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl.make(ParameterizedTypeImpl.java:95)
	at sun.reflect.generics.factory.CoreReflectionFactory.makeParameterizedType(CoreReflectionFactory.java:105)
	at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:140)
	at sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:49)
	at sun.reflect.generics.repository.MethodRepository.getReturnType(MethodRepository.java:68)
	at java.lang.reflect.Method.getGenericReturnType(Method.java:245)
	at com.alibaba.dubbo.rpc.support.RpcUtils.getReturnTypes(RpcUtils.java:73)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DecodeableRpcResult.decode(DecodeableRpcResult.java:82)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DecodeableRpcResult.decode(DecodeableRpcResult.java:109)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboCodec.decodeBody(DubboCodec.java:97)
	at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.decode(ExchangeCodec.java:126)
	at com.alibaba.dubbo.remoting.exchange.codec.ExchangeCodec.decode(ExchangeCodec.java:87)
	at com.alibaba.dubbo.rpc.protocol.dubbo.DubboCountCodec.decode(DubboCountCodec.java:46)
	at com.alibaba.dubbo.remoting.transport.netty.NettyCodecAdapter$InternalDecoder.messageReceived(NettyCodecAdapter.java:134)
	at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)
	at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:274)
	at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:261)
	at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:349)
	at org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:280)
	at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:200)
	at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)
	at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)

定位到代码

sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl#validateConstructorArguments

private void validateConstructorArguments() {
        TypeVariable[] var1 = this.rawType.getTypeParameters();
        if (var1.length != this.actualTypeArguments.length) {
            throw new MalformedParameterizedTypeException();
        } else {
            for(int var2 = 0; var2 < this.actualTypeArguments.length; ++var2) {
            }
        }
    }

debug下发下 var1.length=0 ,而this.actualTypeArguments.length 是1,导致抛出异常.

结合每次查询都是一个查询跑错,发现工程有两个一样的类 .

第一个类是:

public class QueryPageResult implements Serializable {
    public String retcode;
    public String retmsg;
    public String counts;
    public String sum;
    public List resultList;

第二个类是

public class QueryPageResult<T> implements Serializable {
    private static final long serialVersionUID = 6256587973711935282L;
    public String retcode;
    public String retmsg;
    public String counts;
    public String sum;
    public List<T> resultList;