actionManager中的NullPointerExcept

actionManager中的NullPointerExcept

关注
发信
关注(28)粉丝(399)

升级到Spring Boot 1.4.0之后，AbstractPlatformTransactionManager中的NullPointerException

本文介绍了升级到Spring Boot 1.4.0之后，AbstractPlatformTransactionManager中的NullPointerException的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！

问题描述

我已经从Spring Boot 1.3.2升级到1.4.0，但是现在无法启动我的应用程序-我的BeanPostProcessor调用3d第三方开源Lazy Chopper，当尝试getTransaction()时，它又在这里失败:

I have upgraded from Spring Boot 1.3.2 to 1.4.0, and now fail to start my application -My BeanPostProcessor invokes the 3d party open source Lazy Chopper, which in turns, when attempting to getTransaction(), fails here:

public abstract class AbstractPlatformTransactionManager implements PlatformTransactionManager, Serializable {

    protected transient Log logger = LogFactory.getLog(getClass());
    // ...
    @Override
    public final TransactionStatus getTransaction(TransactionDefinition definition) throws TransactionException {
        Object transaction = doGetTransaction();

        // Cache debug flag to avoid repeated checks.
        boolean debugEnabled = logger.isDebugEnabled(); // logger is null here

当我在此处放置一个断点时，我可以看到logger确实是null，但是值得一提的是，如果我自己在该处调用LogFactory.getLog(getClass())，我的确会找到正确的记录器.

When I place a breakpoint right there, I can see logger is indeed null, but if it's worth mentioning that if I invoke LogFactory.getLog(getClass()) myself right there, I do get the right logger.

似乎我的bean在初始化正确的Logger之前以某种方式调用了该方法?.

It seems as if somehow my bean's invoking that method prior to the right Logger being initialized?..

这是我得到的完整堆栈跟踪:

Here's the full stack trace I got:

Caused by: java.lang.NullPointerException: null
at org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:340) ~[spring-tx-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.transaction.interceptor.TransactionAspectSupport.createTransactionIfNecessary(TransactionAspectSupport.java:426) ~[spring-tx-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:275) ~[spring-tx-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96) ~[spring-tx-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:168) ~[spring-aop-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:85) ~[spring-aop-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at com.tikal.lazychopper.DefaultLazyInitializationChopperAdvice.chop(DefaultLazyInitializationChopperAdvice.java:76) ~[lazy-chopper-1.2.8.jar:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_101]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_101]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_101]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_101]
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:629) ~[spring-aop-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:618) ~[spring-aop-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:70) ~[spring-aop-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:168) ~[spring-aop-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655) ~[spring-aop-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at com.sapiens.bdms.core.service.impl.sign.hash.MD5StringCalculator$$EnhancerBySpringCGLIB$$b5747fb.getSignTypes(<generated>) ~[classes/:na]
at com.sapiens.bdms.core.service.impl.sign.EntitySignCalculatorManagerImpl.postProcessAfterInitialization(EntitySignCalculatorManagerImpl.java:105) ~[classes/:na]
at com.sapiens.bdms.core.service.impl.sign.EntitySignCalculatorManagerImpl$$FastClassBySpringCGLIB$$80ef4d8e.invoke(<generated>) ~[classes/:na]
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) ~[spring-core-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720) ~[spring-aop-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157) ~[spring-aop-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92) ~[spring-aop-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179) ~[spring-aop-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655) ~[spring-aop-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at com.sapiens.bdms.core.service.impl.sign.EntitySignCalculatorManagerImpl$$EnhancerBySpringCGLIB$$91a9897b.postProcessAfterInitialization(<generated>) ~[classes/:na]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsAfterInitialization(AbstractAutowireCapableBeanFactory.java:422) ~[spring-beans-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1583) ~[spring-beans-4.3.2.RELEASE.jar:4.3.2.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545) ~[spring-beans-4.3.2.RELEASE.jar:4.3.2.RELEASE]

我使用的是默认的logback自动配置，没有任何调整.

I'm using the default logback auto configuration, no tweaks.

更新#1:围绕该方法定义了切入点.

Update #1:There's point cut defined around that method.

            <aop:pointcut id="transactionManagerPointcut"
                      expression="(execution(* org.springframework.transaction.PlatformTransactionManager.getTransaction(..)))"/>

更新#2:因此，摆脱这一方面似乎可以解决问题.仍然试图找出原因和克服方法.

Update #2:So it seems getting rid of that aspect did the trick.. Still trying to figure out why and how to overcome this.

这是方面的定义:

            <aop:pointcut id="transactionManagerPointcut"
                      expression="(execution(* org.springframework.transaction.PlatformTransactionManager.getTransaction(..)))"/>

        <aop:pointcut id="allServices"
                      expression="(execution(* com.decision..tx..*.*(..))) or (execution(* com.sapiens.bdms..tx..*.*(..))) &amp;&amp; !@annotation(com.sapiens.bdms.core.persistence.annotation.NotTransactional)"/>
        <aop:aspect ref="sessionFilterConfigurator">
            <aop:before method="setupFilter"
                        pointcut-ref="allServices"/>
            <aop:after-returning method="setupFilter"
                                 pointcut-ref="transactionManagerPointcut"/>
        </aop:aspect>

这是Aspect方法:

And here's the aspect method:

    @Component("sessionFilterConfigurator")
public class SessionFilterConfigurator {
    @Resource
    private Collection<FilterConfiguration> filterConfigurations;
    @Resource
    private SessionFactory sessionFactory;
    @Resource
    private FiltersDisconnector filtersDisconnector;

    public void setupFilter() throws Throwable {
        Session session = sessionFactory.getCurrentSession();
        if (AutoEnableConfig.isFiltersEnabled()) {
            for (FilterConfiguration filterConfiguration : filterConfigurations) {
                Filter filter = session.enableFilter(filterConfiguration.getFilterName());
                for (Map.Entry<String, Object> entry : filterConfiguration.getFilterParameters().entrySet()) {
                    filter.setParameter(entry.getKey(), entry.getValue());
                }
            }
            AutoEnableConfig.disableFilterEnabling();
            ((EventSource) session).getActionQueue().registerProcess(filtersDisconnector);
        }
    }
}

关于在这种情况下为什么会破坏记录器，以及为何仅在升级到1.4.0后为何仍不清楚...

Still not clear as to why would that break the logger in this instance, and why only after upgrading to 1.4.0 ...

推荐答案

我遇到了同样的问题.我的错是由于切入点定义错误，我最终将方面应用于TransactionManager(我扩展了标准的方面).因此，空记录器是CGLIB生成的扩展类之一.真正的bean的记录器很好地实例化了.

I had the very same problem. My fault was that due to wrong pointcut definition I ended up applying aspect onto TransactionManager (I had the standard one extended). So the null logger was the one of the CGLIB's generated extended class. The real bean had its logger nicely instantiated.

这篇关于升级到Spring Boot 1.4.0之后，AbstractPlatformTransactionManager中的NullPointerException的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！

08-18 23:10
Powered by LMLPHP ©2024 actionManager中的NullPointerExcept 0.032911