如何在运行时更改log4j2.xml中的记录程序级别而不重新启动tomcat服务 [英] How to change logger level in log4j2.xml at runtime without restarting tomcat service

查看:120
本文介绍了如何在运行时更改log4j2.xml中的记录程序级别而不重新启动tomcat服务的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我以前使用过log4j 1.2,最近又迁移到了log4j 2.0我在web.xml的log4j 1.2中使用了以下侦听器类

I was using log4j 1.2 earlier and I recently migrated to log4j 2.0 I was using below listener class in log4j 1.2 in web.xml

<listener>
    <listener-class>org.springframework.web.util.Log4jConfigListener</listener-class>
</listener> 

在log4j 2.0之后,此侦听器类已删除,我希望替换此侦听器类,这使我可以在运行时更改记录器级别并进行更新,而无需重新启动Web应用程序中的tomcat服务.

This listener class is removed after log4j 2.0 and I want replacement of this listener class which allow me to change logger level at runtime and update without restarting tomcat service in my web application.

我已经在下面的监听器中尝试过了,但这同时在更改log4j2.xml中的配置时也重新启动了Tomcat

I have tried below listener but this is also restarting tomcat while changing configuration in log4j2.xml

 <listener>
        <listener-class>org.apache.logging.log4j.core.web.Log4jContextListener</listener-class>
 </listener>

在更改log4j2.xml时,我在下面看到异常和警告,然后重新启动tomcat:

I am seeing below Exceptions and warnings while changing log4j2.xml and then it restarts tomcat:

WARNING: The web application [demo] appears to have started a thread named [pool-UCCAdminMonitor-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.parkNanos(Unknown Source)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(Unknown Source)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source)
 java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(Unknown Source)
 java.util.concurrent.ThreadPoolExecutor.getTask(Unknown Source)
 java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
 java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
 java.lang.Thread.run(Unknown Source)
Jul 14, 2020 8:36:25 AM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads

Exception in thread "Log4j2-TF-10-ConfiguratonFileWatcher-19" java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [META-INF/services/javax.xml.parsers.DocumentBuilderFactory]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
    at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1385)
    at org.apache.catalina.loader.WebappClassLoaderBase.findResources(WebappClassLoaderBase.java:985)
    at org.apache.catalina.loader.WebappClassLoaderBase.getResources(WebappClassLoaderBase.java:1086)
    at java.util.ServiceLoader$LazyIterator.hasNextService(Unknown Source)
    at java.util.ServiceLoader$LazyIterator.hasNext(Unknown Source)
    at java.util.ServiceLoader$1.hasNext(Unknown Source)
    at javax.xml.parsers.FactoryFinder$1.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at javax.xml.parsers.FactoryFinder.findServiceProvider(Unknown Source)
    at javax.xml.parsers.FactoryFinder.find(Unknown Source)
    at javax.xml.parsers.DocumentBuilderFactory.newInstance(Unknown Source)
    at org.apache.logging.log4j.core.config.xml.XmlConfiguration.newDocumentBuilder(XmlConfiguration.java:183)
    at org.apache.logging.log4j.core.config.xml.XmlConfiguration.<init>(XmlConfiguration.java:89)
    at org.apache.logging.log4j.core.config.xml.XmlConfiguration.reconfigure(XmlConfiguration.java:272)
    at org.apache.logging.log4j.core.LoggerContext.onChange(LoggerContext.java:752)
    at org.apache.logging.log4j.core.util.AbstractWatcher$ReconfigurationRunnable.run(AbstractWatcher.java:92)
    at java.lang.Thread.run(Unknown Source)

INFO: Illegal access: this web application instance has been stopped already. Could not load [org.apache.logging.log4j.core.lookup.JndiLookup]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [org.apache.logging.log4j.core.lookup.JndiLookup]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
    at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1385)
    at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1373)
    at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1226)
    at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1188)
    at org.apache.logging.log4j.util.LoaderUtil.loadClass(LoaderUtil.java:167)
    at org.apache.logging.log4j.util.LoaderUtil.newInstanceOf(LoaderUtil.java:209)
    at org.apache.logging.log4j.util.LoaderUtil.newCheckedInstanceOf(LoaderUtil.java:230)
    at org.apache.logging.log4j.core.util.Loader.newCheckedInstanceOf(Loader.java:311)
    at org.apache.logging.log4j.core.lookup.Interpolator.<init>(Interpolator.java:112)
    at org.apache.logging.log4j.core.config.AbstractConfiguration.<init>(AbstractConfiguration.java:129)
    at org.apache.logging.log4j.core.config.xml.XmlConfiguration.<init>(XmlConfiguration.java:76)
    at org.apache.logging.log4j.core.config.xml.XmlConfiguration.reconfigure(XmlConfiguration.java:272)
    at org.apache.logging.log4j.core.LoggerContext.onChange(LoggerContext.java:752)
    at org.apache.logging.log4j.core.util.AbstractWatcher$ReconfigurationRunnable.run(AbstractWatcher.java:92)

推荐答案

回答我自己的问题-首先需要在web.xml中添加以下过滤器和侦听器:

Answering my own question - First need to add below filter and listener in web.xml :

    <listener>
        <listener-class>org.apache.logging.log4j.web.Log4jServletContextListener</listener-class>
    </listener>
 
    <filter>
        <filter-name>log4jServletFilter</filter-name>
        <filter-class>org.apache.logging.log4j.web.Log4jServletFilter</filter-class>
    </filter>
    <filter-mapping>
        <filter-name>log4jServletFilter</filter-name>
        <url-pattern>/*</url-pattern>
        <dispatcher>REQUEST</dispatcher>
        <dispatcher>FORWARD</dispatcher>
        <dispatcher>INCLUDE</dispatcher>
        <dispatcher>ERROR</dispatcher>
        <dispatcher>ASYNC</dispatcher><!-- Servlet 3.0 w/ disabled auto-initialization only; not supported in 2.5 -->
    </filter-mapping>

log4j2.xml的

路径应为/WEB-INF/log4j2.xml此后,当我们更改记录器级别时,它将不会重新启动tomcat服务.

path of log4j2.xml should be /WEB-INF/log4j2.xml After this while we change logger level it will not restart the tomcat service.

这篇关于如何在运行时更改log4j2.xml中的记录程序级别而不重新启动tomcat服务的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆