反射优化引发的问题

记录一次压测中遇到的线程阻塞问题
java能够使用反射来执行方法调用,反射根据一个类名获得Class对象,再由对象名和给定的参数集拿到Method对象,就能够经过Method.invoke来执行java

@CallerSensitive
    public Object invoke(Object var1, Object... var2) throws IllegalAccessException, IllegalArgumentException, InvocationTargetException {
        if(!this.override && !Reflection.quickCheckMemberAccess(this.clazz, this.modifiers)) {
            Class var3 = Reflection.getCallerClass();
            this.checkAccess(var3, this.clazz, var1, this.modifiers);
        }
        MethodAccessor var4 = this.methodAccessor;
        if(var4 == null) {
            var4 = this.acquireMethodAccessor();
        }
        return var4.invoke(var1, var2);
    }

由上面的代码能够看出来invoke是由MethodAccessor来执行的,MethodAccessor又是acquireMethodAccessor方法获取到的jvm

private MethodAccessor acquireMethodAccessor() {
        MethodAccessor var1 = null;
        if(this.root != null) {
            var1 = this.root.getMethodAccessor();
        }
        if(var1 != null) {
            this.methodAccessor = var1;
        } else {
            var1 = reflectionFactory.newMethodAccessor(this); 
            this.setMethodAccessor(var1);
        }
        return var1;
    }

MethodAccessor是经过ReflectionFactory的newMethodAccessor获取的,代码以下:ide

public MethodAccessor newMethodAccessor(Method var1) {
        checkInitted();
        if(noInflation && !ReflectUtil.isVMAnonymousClass(var1.getDeclaringClass())) {
            return (new MethodAccessorGenerator()).generateMethod(var1.getDeclaringClass(), var1.getName(), var1.getParameterTypes(), var1.getReturnType(), var1.getExceptionTypes(), var1.getModifiers());
        } else {
            NativeMethodAccessorImpl var2 = new NativeMethodAccessorImpl(var1);
            DelegatingMethodAccessorImpl var3 = new DelegatingMethodAccessorImpl(var2);
            var2.setParent(var3);
            return var3;
        }
    }

若是noInflation为true(不膨胀,当Java虚拟机从JNI存取器改成字节码存取器的行为被称为膨胀(Inflation)),建立MethodAccessorGenerator,不然NativeMethodAccessor。NativeMethodAccessorImpl中的invoke代码以下优化

public Object invoke(Object var1, Object[] var2) throws IllegalArgumentException, InvocationTargetException {
        if(++this.numInvocations > ReflectionFactory.inflationThreshold() && !ReflectUtil.isVMAnonymousClass(this.method.getDeclaringClass())) {
            MethodAccessorImpl var3 = (MethodAccessorImpl)(new MethodAccessorGenerator()).generateMethod(this.method.getDeclaringClass(), this.method.getName(), this.method.getParameterTypes(), this.method.getReturnType(), this.method.getExceptionTypes(), this.method.getModifiers());
            this.parent.setDelegate(var3);//当这一步执行完以后,DelegatingMethodAccessorImpl中的delegate就是MethodAccessorImpl而不是NativeMethodAccessorImpl了
        }
        return invoke0(this.method, var1, var2);
    }

ReflectionFactory.inflationThreshold() 就是jvm的启动参数的-Dsun.reflect.inflationThreshold,默认值是15.ui

调用次数没有超过这个阈值的时候其实使用的仍是NativeMethodAccessor.invoke),即没有if里面那些处理。超出阈值后执行if中的逻辑,native的就被搞成了MethodAccessorImpl。同时setDelegatethis

这个setDelegate 要回看上面DelegatingMethodAccessorImpl,有点像一个中间层,在native和java版之间转换线程

class DelegatingMethodAccessorImpl extends MethodAccessorImpl {
    private MethodAccessorImpl delegate;
    DelegatingMethodAccessorImpl(MethodAccessorImpl var1) {
        this.setDelegate(var1);
    }
    public Object invoke(Object var1, Object[] var2) throws IllegalArgumentException, InvocationTargetException {
        return this.delegate.invoke(var1, var2);
    }
    void setDelegate(MethodAccessorImpl var1) {
        this.delegate = var1;
    }
}

听说java版的启动慢,可是执行快(编译器能够优化);native版的启动快,可是执行慢。因此hotspot的jdk作了个优化,调用次数少时用native版的,当发现调用次数多时,则调用MethodAccessorGenerator.generateMethod()来生成Java版的MethodAccessor的实现类,而且改变DelegatingMethodAccessorImpl所引用的MethodAccessor为Java版code

sun.reflect.GeneratedMethodAccessor<N>是怎么出现的呢?对象

默认这个优化是开启的且阈值是15,在前面少数调用时,调用的实际上是native版的invoke0,超出阈值后,就开始使用MethodAccessorGenerator.generateMethod,这里面最终会调到一个genarateName方法get

private static synchronized String generateName(boolean var0, boolean var1) {
        int var2;
        if(var0) {
            if(var1) {
                var2 = ++serializationConstructorSymnum;
                return "sun/reflect/GeneratedSerializationConstructorAccessor" + var2;
            } else {
                var2 = ++constructorSymnum;
                return "sun/reflect/GeneratedConstructorAccessor" + var2;
            }
        } else {
            var2 = ++methodSymnum;
            return "sun/reflect/GeneratedMethodAccessor" + var2;
        }
    }
相关文章
相关标签/搜索