解决maven升级log4j2版本后报ERROR错误

项目为spring mvc，在升级log4j2版本后，在每次启动server会报一堆StatusLogger的ERROR，但是能够正常使用，log也有正常的文件记录，具体的错误log如下：

ERROR StatusLogger Caught java.lang.AbstractMethodError setting feature http://xml.org/sax/features/external-general-entities to false on DocumentBuilderFactory org.apache.xerces.jaxp.DocumentBuilderFactoryImpl@723b1d: java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature(Ljava/lang/String;Z)V
    java.lang.AbstractMethodError: javax.xml.parsers.DocumentBuilderFactory.setFeature(Ljava/lang/String;Z)V
   	at org.apache.logging.log4j.core.config.xml.XmlConfiguration.setFeature(XmlConfiguration.java:212)
   	at org.apache.logging.log4j.core.config.xml.XmlConfiguration.disableDtdProcessing(XmlConfiguration.java:205)
   	at org.apache.logging.log4j.core.config.xml.XmlConfiguration.newDocumentBuilder(XmlConfiguration.java:194)
   	at org.apache.logging.log4j.core.config.xml.XmlConfiguration.<init>(XmlConfiguration.java:92)
   	at org.apache.logging.log4j.core.config.xml.XmlConfigurationFactory.getConfiguration(XmlConfigurationFactory.java:46)
   	at org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:453)
   	at org.apache.logging.log4j.core.config.ConfigurationFactory$Factory.getConfiguration(ConfigurationFactory.java:385)
   	at org.apache.logging.log4j.core.config.ConfigurationFactory.getConfiguration(ConfigurationFactory.java:260)
   	at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:615)
   	at org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:636)
   	at org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:231)
   	at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:153)
   	at org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
   	at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
   	at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:121)
   	at org.apache.logging.slf4j.Log4jLoggerFactory.getContext(Log4jLoggerFactory.java:43)
   	at org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:46)
   	at org.apache.logging.slf4j.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:29)
   	at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:358)
   	at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:156)
   	at org.apache.commons.logging.impl.SLF4JLogFactory.getInstance(SLF4JLogFactory.java:132)
   	at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:657)
   	at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:304)
   	at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:107)
   	at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4738)
   	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5181)
   	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
   	at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)
   	at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)
   	at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)
   	at org.apache.catalina.startup.HostConfig.manageApp(HostConfig.java:1678)
   	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
   	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   	at java.lang.reflect.Method.invoke(Method.java:498)
   	at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300)
   	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
   	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
   	at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:463)
   	at org.apache.catalina.mbeans.MBeanFactory.createStandardContext(MBeanFactory.java:413)
   	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
   	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   	at java.lang.reflect.Method.invoke(Method.java:498)
   	at org.apache.tomcat.util.modeler.BaseModelMBean.invoke(BaseModelMBean.java:300)
   	at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:819)
   	at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:801)
   	at com.sun.jmx.remote.security.MBeanServerAccessController.invoke(MBeanServerAccessController.java:468)
   	at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
   	at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
   	at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
   	at java.security.AccessController.doPrivileged(Native Method)
   	at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1408)
   	at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
   	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
   	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   	at java.lang.reflect.Method.invoke(Method.java:498)
   	at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:357)
   	at sun.rmi.transport.Transport$1.run(Transport.java:200)
   	at sun.rmi.transport.Transport$1.run(Transport.java:197)
   	at java.security.AccessController.doPrivileged(Native Method)
   	at sun.rmi.transport.Transport.serviceCall(Transport.java:196)
   	at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:568)
   	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:826)
   	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.lambda$run$0(TCPTransport.java:683)
   	at java.security.AccessController.doPrivileged(Native Method)
   	at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:682)
   	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
   	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
   	at java.lang.Thread.run(Thread.java:748)

经过调查该问题为xml解析器问题，通过log第一行(XmlConfiguration.java:212)可以定位问题发生在org.apache.logging.log4j.core.config.xml.XmlConfiguration.setFeature这个函数。
通过查看源码可以发现该方法为抽象方法，而通过idea可以查找到在哪实现了这个方法，通过排查发现DocumentBuilderFactory这个类有org.apache.xerces.jaxp.DocumentBuilderFactoryImpl这里进行实现，而这个方法没有setFeature这个方法，至此可以得出结论，jar包冲突导致了问题发生，
那么只要排查掉这个包就可以了，通过idea的定位可以知道这个类在xerces:xercesImpl中，然后通过依赖树可以定位到它在org.apache.axis2:axis2-java2wsdl这个jar包中，通过module setting的find usages功能可以知道这个包实际没有使用，那么只要加入排除即可解决问题，即maven改为如下：

<dependency>
    <groupId>org.apache.axis2</groupId>
    <artifactId>axis2-java2wsdl</artifactId>
    <version>1.5.1</version>
    <exclusions>
        <exclusion>
            <groupId>xerces</groupId>
            <artifactId>xercesImpl</artifactId>
        </exclusion>
    </exclusions>
</dependency>

更改后经验证已解决问题

感谢@流浪的侠客 https://blog.youkuaiyun.com/yechaodechuntian/article/details/78974894 提供的思路