log4j:ERROR LogMananger.repositorySelector was null likely due to error in class

最新推荐文章于 2019-03-21 10:55:28 发布
原创 最新推荐文章于 2019-03-21 10:55:28 发布 · 3.8k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#log4j #null #class #ssh

本文记录了SSH整合过程中遇到的一个关于log4j1.2.15的bug，该bug导致错误日志输出，影响正常运行。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

SSH整合出现

Log4j 1.2.15存在一个bug

epfeng
关注
什么是In-Memory计算？ Mastering In Memory Computing:A Comprehensive Guide
AI天才研究院
07-20 3179
作者：禅与计算机程序设计艺术 什么是In-Memory计算？ In-memory computing refers to the process of executing computational tasks by storing input and output data i
camera自动升级失败问题
b178903294的博客
04-04 2018
camera自动升级过程中失败: 只有自动升级时才会失败，手动点击升级时是正常的。 自动升级和手动升级调用的接口是完全一样的，并且都是通过EventBus 接收升级的event调用同一段函数进行处理，所以函数调用上没有任何区别，显然不是代码逻辑的错误。 通过查看失败的log发现connect camera时超时了： 折叠源码 ... UsbInterface[mId=1,mAlternateSetting=9,mName=null,mCla...
log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using ...
dianchaozong3657的博客
08-18 173
The reason for the error is a new listener in Tomcat 6.0.24. You can fix this error by adding this line: org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false to the "conf/...
log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NO
海洋专栏
03-24 4463
log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository的解决方法 eclipse里启动server时,发现日志里打印了一条ERROR级别的日志,查了一些资料,原因是说,在tomcat6.0增加了一个 监听
解决log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading问题
@Banana的博客
03-21 2931
错误常常是正确的先导。-----------Banana • Banuit Gang(香柚帮) 每次关闭tomcat6.0之后都会出现一条这样的信息，虽然不影响程序运行，但是看到error，心情总是不好的。去网上查找一番，说是版本问题，改为log4j-1.2.14.jar就不会出现了，但是我的jar包本来就是这个呀，那肯定不是jar包版本的问题了，然后继续找是哪里的问题，在网上又看到说tom...
log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using N
tony的专栏
08-16 3907
Log4j 1.2.15存在一个bug会导致log4j:ERROR LogMananger.repositorySelector was null likely due to  于是我换成了Log4j 1.2.14版本，问题解决了！
log4j-1.2.14.jar
12-01
1.2.15有个Bug，会提示log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository，大家使用1.2.14替换1.2.15即可解决！
01-Jul-2025 18:26:22.896 SEVERE [RMI TCP Connection(3)-127.0.0.1] org.apache.catalina.core.StandardContext.startInternal Context [/ecm-sf5-cn] startup failed due to previous errors 01-Jul-2025 18:26:22.968 WARNING [RMI TCP Connection(3)-127.0.0.1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ecm-sf5-cn] appears to have started a thread named [Catalina-utility-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: org.apache.catalina.core.StandardContext.backgroundProcess(StandardContext.java:4825) org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1172) org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1176) org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1176) org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1154) java.base@17.0.12/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) java.base@17.0.12/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) java.base@17.0.12/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) java.base@17.0.12/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) java.base@17.0.12/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63) java.base@17.0.12/java.lang.Thread.run(Thread.java:840) 01-Jul-2025 18:26:22.968 WARNING [RMI TCP Connection(3)-127.0.0.1] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ecm-sf5-cn] appears to have started a thread named [DefaultQuartzScheduler_QuartzSchedulerThread] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.base@17.0.12/java.lang.Object.wait(Native Method) org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:427) 01-Jul-2025 18:26:22.977 SEVERE [RMI TCP Connection(3)-127.0.0.1] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [ecm-sf5-cn] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@3777677a]) and a value of type [com.documentum.web.env.app.AppServerEnvironment] (value [[Name = App Server Environment, Description = App Server Environment Implementation, Major Version = 0, Minor Version = 1, Author = Documentum, Portal Description = App Server, Portal Version = x.x, Environment Base Version = 1.0, Environment Service Version = 6.0, Supports Dispatch Contract = true, Supports Theme Contract = true, Supports Error Contract = true, Supports FormOperationListener Contract = false, Supports Locale Contract = true, Supports Session Contract = true, Supports Tag Contract = false, Supports Render Contract = true, Supports Login Contract = false, Supports Security Contract = true, Supports ActionPrecondition Contract = false, Supports MessageService Contract = false, Supports SuperCredentials Contract = true, Supports Preference Contract = true, Supports ContentTransfer Contract = true]]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak. [2025-07-01 06:26:22,998] Artifact ecm-sf5-cn: Error during artifact deployment. See server log for details.
最新发布
07-02
**查看详细日志**：错误信息提到“Fulldetails willbe foundin theappropriate containerlog file”（引用[3]），因此需要检查Tomcat的日志文件（如catalina.out或localhost.log）以确定哪个监听器或组件失败。...
ERROR ContextLoader:351 - Context initialization failed
xman2008wang的博客
11-19 3831
今天在做bos项目第3天的代码: [INFO] Scanning for projects... [INFO] [INFO] -----------------------------------------------------------------
LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepo
schenjiannan的专栏
04-01 1887
LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository. 如何解决
log4j:ERROR LogMananger.repositorySelector was null
a13969726756的专栏
05-25 187
排除log4j版本问题后，仍出现此问题，解决方法：在Tomcat安装目录下conf/catalina.properties文件中设置org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES=false。 去Tomcat网站上查看了它的含义： http://tomcat.apache.org/tomcat-6...
'log4j:ERROR LogMananger.repositorySelector was null'解决方法
Jasonwu的专栏
10-20 6864
在Eclipse中，在 tomcat6中重新启动时出现错误信息：log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository. 解决方法： 在tomcat的"conf/catalina.properties“文件中末尾
Log4j常见错误
xiaolong0211的专栏
02-16 340
1、 log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository. 今天在linux上部署公司项目，启动tomcat登陆后，工作台提示如上错误，我用的log4j版本是log4j-1.2.15.jar，网上...
abaqus出现Error in job bibibi: Memory errors occured while parsing 1 keywords. The errors were likely due to running out of physical memory or swap space. Error in job bibibi: Multiple error messages. Error in job bibibi: ERROR DURING PART, INSTANCE AND ASSEMBLY PROCESSING Job bibibi: Analysis Input File Processor aborted due to errors. Job bibibi: Analysis Input File Processor aborted due to errors. Error in job bibibi: Analysis Input File Processor exited with an error - Please see the bibibi.dat file for possible error messages if the file exists. Job bibibi aborted due to errors.
03-22
好的，我现在需要帮助用户解决Abaqus运行时出现的内存不足错误，具体是“Error in job: Analysis Input File Processor aborted”的问题。首先，我应该回顾用户提供的引用资料，看看有没有相关的线索。 用户提到的...
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值