Log4jConflictsInJBoss

解决JBoss中Log4j冲突问题

最新推荐文章于 2025-11-24 11:56:09 发布

原创最新推荐文章于 2025-11-24 11:56:09 发布 · 117 阅读

0 ·

CC 4.0 BY-SA版权

文章标签：

#log4j #JBoss #Apache #.net #Web

Application Service 专栏收录该内容

1 篇文章

订阅专栏

本文解决了一个常见的JBoss应用服务器上的部署问题，即应用程序打包了Log4j和Commons-Logging相关的JAR文件导致的异常冲突。文章详细介绍了如何通过移除这些JAR文件来解决冲突。

Problem:

You see exceptions similar to:

20:05:44,757 ERROR STDERR log4j:ERROR A "org.jboss.logging.util.OnlyOnceErrorHandler" object is not assignable to a "org.apache.log4j.spi.ErrorHandler" variable.

20:05:44,757 ERROR STDERR log4j:ERROR The class "org.apache.log4j.spi.ErrorHandler" was loaded by

20:05:44,757 ERROR STDERR log4j:ERROR [WebappClassLoaderDelegateFalseRepositories/WEBINF/Classes/ParentClassloaderjava.net.FactoryURLClassLoader31c43f|WebappClassLoader delegate: false repositories: /WEB-INF/classes/ -

> Parent Classloader: java.net.FactoryURLClassLoader@31c43f ] whereas object of type

20:05:44,757 ERROR STDERR log4j:ERROR "org.jboss.logging.util.OnlyOnceErrorHandler" was loaded by Org.jboss.system.server.NoAnnotationURLClassLoaderab95e6 .

20:05:44,820 ERROR STDERR log4j:ERROR Could not create an Appender. Reported error follows.

Solution:

These sort of exceptions occur if an application deployed on JBoss packages log4j and commons-logging related jars in its package. JBoss has its own versions of these jars in its lib folder which results in these conflicts.

Removing the log4j and commons-logging jars from your application's package will solve this issue.