AnsweredAssumed Answered

CA APM Agent log4j conflict

Question asked by TulioBarbosa on Jan 8, 2016
Latest reply on Jan 11, 2016 by Hallett_German

Hi there, we are facing the following problem when the agent is turned on with logging:

 

ERROR [stderr] (MSC service thread 1-1) log4j:ERROR Could not instantiate class [org.jboss.logging.appender.FileAppender].

ERROR [stderr] (MSC service thread 1-1) java.lang.ClassNotFoundException: org.jboss.logging.appender.FileAppender from [Module "org.jboss.log4j.logmanager:main" from local mo     dule loader @17496e57 (roots: /rede/jboss-eap-6.0.1/modules)]

ERROR [stderr] (MSC service thread 1-1) log4j:ERROR Could not instantiate appender named "FILE".

 

The parameters that we start the jvm:

 

JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager"

JAVA_OPTS="$JAVA_OPTS -Xbootclasspath/p:/opt/jboss-eap-6.0.1/modules/org/jboss/logmanager/main/jboss-logmanager-1.3.2.Final-redhat-1.jar"

JAVA_OPTS="$JAVA_OPTS -javaagent:/opt/wily_10/Agent.jar -Dcom.wily.introscope.agentProfile=/opt/wily_10/core/config/IntroscopeAgent.jboss.profile"

JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman,org.jboss.logmanager,com.wily,com.wily.*"

 

Seems like a library conflict issue but we cannot identified it. Our application server is JBoss EAP 6.0.1 with Java Oracle 1.6.0_23, CentOS 5.5.

This error is not crashing the jboss neither the agent but is flooding our logs.

 

Thanks in advance.

Outcomes