关于log4j:ERROR Attempted to append toclosed异常

最新推荐文章于 2020-06-23 11:45:10 发布
原创 最新推荐文章于 2020-06-23 11:45:10 发布 · 815 阅读 · 1 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#log4j #closed

本文介绍了一位同事遇到的Log4j配置错误问题：尝试向已关闭的追加器写入日志。通过排查发现，问题根源在于项目依赖中存在多个Log4j配置文件。文章建议检查项目的类路径是否存在多余的Log4j配置文件。
今天在某人的机器发现：

log4j:ERROR Attempted to append to closed appender named [A1].



他和我用相同的配置文件，我没有异常，而他有



经过排查，实际很简单，就是因为他的某个依赖工程有另外一个log4j.properties文件存在，导致了上述异常。



所以当你碰到类似的问题，请检查classpath是否还有其他的Log4j.properties文件。
摘自:http://blog.sina.com.cn/s/blog_58c679ff01009w7i.html
meixiangnila
关注
log4j源码解析及一个log4j:ERROR Attempted to append to closed appender named 的问题
专注海量数据
06-08 2万+
一、log4j源码解析 最近出现一个问题，弄得我不得不把log4j的源代码读了一篇。 如果自己不想写代码，可以下载此代码：https://github.com/lwwcl1314/atlantis/tree/master/common/src/main/java/com/atlantis/study/log 先讲下log4j的设计. log4j主要有元素：logger leve
掌握 Java 领域 log4j，提升日志记录效率
最新发布
Java大师兄的博客
06-23 692
本文旨在帮助Java开发者全面掌握log4j日志框架的使用，从基础配置到高级特性，最终实现高效、灵活的日志记录系统。内容涵盖log4j 2.x版本的核心功能，包括配置、日志级别、Appender、Filter等关键概念。文章从log4j基础概念开始，逐步深入到高级配置和性能优化，最后通过实际案例展示最佳实践。Logger: 日志记录器，应用程序通过Logger实例记录日志Appender: 日志输出目的地，如控制台、文件、数据库等Layout: 日志输出格式定义Filter。
log4j:ERROR Attempted to append to closed appender named [INFO-ALL].
业精于勤荒于嬉;行成于思，毁于随。
12-09 3159
log4j 是我们程序开发者常用的日志记录工具。 但是使用过程中可能会遇到一些问题，因为是采用配置文件的方式，这样就不可控。 比如遇到了下面这种情况。 tomcat的stderr文件中一直在打印下面这些错误，打印少点还好，但是太多就不好了，因为这个文件一天一个，有时一个将近700M大小。 log4j:ERROR Attempted to append to closed appende
log4j:ERROR Attempted to append to closed appender named [*]
u012780541的博客
12-22 688
  During system running, sometimes we can see the error message from log4j log:   log4j:ERROR Attempted to append to closed appender named [*].   Here I would like to talk about one use case whic...
log4j:ERROR Attempted to append to closed appender named [null].
如来
08-17 4169
最近用Velocity总是出现以下消息log4j:ERROR Attempted to append to closed appender named [null]. 试了很多方法未果，最后到Velocity 的build/lib包里看了一下，发现有个包叫logkit-1.0.1.jar于是加到项目中，解决此问题
log4j:ERROR Attempted to append to closed appender named [CONSOLE].
星光熠熠 的专栏
10-17 9388
最近开发时，程序控制台日志中经常出现一些这种报错： log4j:ERROR Attempted to append to closed appender named [CONSOLE]. 问题原因：经过检查发现，在lo4j配置文件中，将一个appender重复配置了，如下： --第1处配置 log4j.appender.ROLLING_FILE_INPUTER=org.apache.log4
springaialibaba项目启动出现大量警告:16:00:24,057 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - 'File' option has the same value "C:\Users\Dai52/logs/nacos/config.log" as that given for appender [CONFIG_LOG_FILE] defined earlier. 16:00:24,058 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Collisions detected with FileAppender/RollingAppender instances defined earlier. Aborting. 16:00:24,058 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - For more information, please visit https://logback.qos.ch/codes.html#earlier_fa_collision 16:00:24,059 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[NAMING_LOG_FILE] - 'File' option has the same value "C:\Users\Dai52/logs/nacos/naming.log" as that given for appender [NAMING_LOG_FILE] defined earlier. 16:00:24,059 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[NAMING_LOG_FILE] - Collisions detected with FileAppender/RollingAppender instances defined earlier. Aborting. 16:00:24,059 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[NAMING_LOG_FILE] - For more information, please visit https://logback.qos.ch/codes.html#earlier_fa_collision 16:00:24,060 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - 'File' option has the same value "C:\Users\Dai52/logs/nacos/remote.log" as that given for appender [REMOTE_LOG_FILE] defined earlier. 16:00:24,061 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Collisions detected with FileAppender/RollingAppender instances defined earlier. Aborting. 16:00:24,061 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - For more information, please visit https://logback.qos.ch/codes.html#earlier_fa_collision 2025-05-28T16:00:24.067+08:00 INFO 23488 --- [SpringAI-ALibaba] [ main] com.dai.SpringAiAlibabaApplication : Starting SpringAiAlibabaApplication using Java 23.0.1 with PID 23488 (D:\JavaWeb\SpringAI-Alibaba\target\classes started by Dai52 in D:\JavaWeb\SpringAI-Alibaba) 2025-05-28T16:00:24.067+08:00 INFO 23488 --- [SpringAI-ALibaba] [ main] com.dai.SpringAiAlibabaApplication : No active profile set, falling back to 1 default profile: "default" 2025-05-28T16:00:24.684+08:00 WARN 23488 --- [SpringAI-ALibaba] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.cloud.nacos.NacosConfigAutoConfiguration' of type [com.alibaba.cloud.nacos.NacosConfigAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). The currently created BeanPostProcessor [nacosAnnotationProcessor] is declared through a non-static factory method on that class; consider declaring it as static instead. 2025-05-28T16:00:24.688+08:00 WARN 23488 --- [SpringAI-ALibaba] [ main] trationDelegate$BeanPostProcessorChecker : Bean 'nacosConfigProperties' of type [com.alibaba.cloud.nacos.NacosConfigProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [nacosAnnotationProcessor]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE. 16:00:24,695 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - 'File' option has the same value "C:\Users\Dai52/logs/nacos/config.log" as that given for appender [CONFIG_LOG_FILE] defined earlier. 16:00:24,695 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Collisions detected with FileAppender/RollingAppender instances defined earlier. Aborting. 16:00:24,695 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - For more information, please visit https://logback.qos.ch/codes.html#earlier_fa_collision 16:00:24,696 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[NAMING_LOG_FILE] - 'File' option has the same value "C:\Users\Dai52/logs/nacos/naming.log" as that given for appender [NAMING_LOG_FILE] defined earlier. 16:00:24,696 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[NAMING_LOG_FILE] - Collisions detected with FileAppender/RollingAppender instances defined earlier. Aborting. 16:00:24,696 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[NAMING_LOG_FILE] - For more information, please visit https://logback.qos.ch/codes.html#earlier_fa_collision 16:00:24,697 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - 'File' option has the same value "C:\Users\Dai52/logs/nacos/remote.log" as that given for appender [REMOTE_LOG_FILE] defined earlier. 16:00:24,697 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Collisions detected with FileAppender/RollingAppender instances defined earlier. Aborting. 16:00:24,697 |-ERROR in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - For more information, please visit https://logback.qos.ch/codes.html#earlier_fa_collision 16:00:24,701 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Attempted to append to non started appender [CONFIG_LOG_FILE]. 16:00:24,701 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Attempted to append to non started appender [CONFIG_LOG_FILE]. 16:00:24,701 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Attempted to append to non started appender [CONFIG_LOG_FILE]. 16:00:24,701 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Attempted to append to non started appender [CONFIG_LOG_FILE]. 16:00:24,701 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Attempted to append to non started appender [CONFIG_LOG_FILE]. 16:00:24,701 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[CONFIG_LOG_FILE] - Attempted to append to non started appender [CONFIG_LOG_FILE]. 16:00:24,728 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Attempted to append to non started appender [REMOTE_LOG_FILE]. 16:00:24,729 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Attempted to append to non started appender [REMOTE_LOG_FILE]. 16:00:24,729 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Attempted to append to non started appender [REMOTE_LOG_FILE]. 16:00:24,729 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Attempted to append to non started appender [REMOTE_LOG_FILE]. 16:00:24,729 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Attempted to append to non started appender [REMOTE_LOG_FILE]. 16:00:24,729 |-WARN in ch.qos.logback.core.rolling.RollingFileAppender[REMOTE_LOG_FILE] - Attempted to append to non started appender [REMOTE_LOG_FILE].
05-30
Logback configuration error detected:'File' option has the same value "xxx.log" as that given for appender [FILE] defined earlier ``` 具体涉及文件包括`nacos-config.log`、`naming.log`、`remote.log`等...
Log4j优化（一）扩展Log4j来实现性能优化的异步日志收集器
ITer_ZC的专栏
04-23 1万+
日志收集在互联网企业尤其是大数据时代是一件非常重要的事情，日志记录着用户行为和系统行为，是一种重要的数据来源。Log4j是Java应用程序使用的最多的一种日志收集工作。目前大量的Java应用程序都使用着Lo4j 1.2.X版本，Log4j 1.X版本饱受诟病的原因是使用了大量的锁，在高并发的情况下影响了系统的性能。这篇简单提供一种思路，说说如何扩展一下Log4j，提升一下Log4j的性能。
log4j:ERROR Attempted to append to closed appender named 的问题
weixin_30580943的博客
11-26 530
一、log4j源码解析 最近出现一个问题，弄得我不得不把log4j的源代码读了一篇。 如果自己不想写代码，可以下载此代码：https://github.com/lwwcl1314/atlantis/tree/master/common/src/main/java/com/atlantis/study/log 先讲下log4j的设计. log4j主要有元素：logger level...
log4j ERROR Attempted to append to closed appender named nu
weixin_43417960的博客
11-18 527
log4j ERROR Attempted to append to closed appender named nu
这个bug很简单-log4j:ERROR Attempted to append to closed appender named
热门推荐
ESOO
03-31 1万+
最近调试log4j的时候，一直遇到这个错误：log4j:ERROR Attempted to append to closed appender named一直未找到原因，看了几篇博客后知道，是有配置重合了，大家看：这是以前的配置文件：这样就会导致，log4j会清楚所有的appender，删除后，问题就排出了，这个bug督促我们，要努力看源码啊！
Attempted to append to closed appender named xxx
iteye_18132的博客
06-08 480
异常描述：将一将公用服务打成JAR包放置到其他工程里面，系统启动时Log4j打印出如上Error，引发LOG4J失效。 异常解决：检查JAR包中的LOG4J的配置是否与工程中现有的LOG4J配置冲突，其中有可能冲突的地方是： 1、Appender的名称与现有工程冲突。 2、现有工程中已经有ROOT配置，JAR中也包含了些配置，引发冲突。 ...
log4j:ERROR
chuntianlong5227的博客
06-25 109
因为项目使用了commons-logging，然而JFinal似乎"排斥"它，占用log4j一直不放，这样log4j不能被它所用，所以得给它加上自己的属性文件commons-logging.properties，里面只能显示调用其它的日志系统了，如： org.apache.common...
工程师实战 | spark通过kafka-appender指定日志输出到kafka引发的死锁
边逛边看边学习
06-23 828
公司的IT运维日志系统，用的spark+kafka架构。工程师们也经常有一些实战心得。转之 在采用log4j的kafka-appender收集spark任务运行日志时，发现提交到yarn上的任务始终ACCEPTED状态，无法进入RUNNING状态，并且会重试两次后超时。期初认为是yarn资源不足导致，但在确认yarn资源充裕的时候问题依旧，而且基本上能稳定复现。 起初是这么配置spark日志输出到kafka的: log4j.rootCategory=INFO, console, kafka log4
velocity造成log增加的解决办法！（log4j:ERROR Attempted to append to cl）
yezi
02-08 607
最近用Velocity总是出现以下消息 log4j:ERROR Attempted to append to closed appender named [null]. 试了很多方法未果，最后到Velocity 的build/lib包里看了一下，发现有个包叫logkit-1.0.1.jar于是加到项目中，解决此问题...
log4j error
Lin's Tech Log
09-18 141
Error info [9/18/14 12:28:43:968 HKT] 000001e1 SystemErr     R log4j:ERROR Attempted to append to closed appender named [hibernateDebugAppender].   发现有多个下面的setting. <logger name="org.hibernate...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值