Upgrade 14.3 to 14.4 and upgrading Jboss from 6.2 to 7.4 sees "Please add log4j-core to the classpath"
search cancel

Upgrade 14.3 to 14.4 and upgrading Jboss from 6.2 to 7.4 sees "Please add log4j-core to the classpath"

book

Article ID: 367125

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

Error seen after startup. 

ERROR [stderr] (MSC service thread 1-6) ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
ERROR [stderr] (default task-1) ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...

ERROR [stderr] (default task-5) ERROR DefaultDispatcherErrorHandler Exception occurred during processing request: java.lang.LinkageError: loader constraint violation: when resolving method "org.apache.logging.log4j.core.config.Configurator.setLevel(Ljava/lang/String;Lorg/apache/logging/log4j/Level;)V" the class loader (instance of org/jboss/modules/ModuleClassLoader) of the current class, com/netegrity/ims/manage/action/DirectoryDispatchAction, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for the method's defining class, org/apache/logging/log4j/core/config/Configurator, have different Class objects for the type org/apache/logging/log4j/Level used in the signature

Environment

Standalone 

14.4, 14.5

Cause

This occurred on Jboss 7.4 after the upgrade of Jboss.

Resolution

This was fixed once client applied Jboss 7.4 Patchset 14.