DX Application Performance Management

Expand all | Collapse all

CA APM Agent log4j conflict

  • 1.  CA APM Agent log4j conflict

    Posted 01-08-2016 08:19 AM

    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.



  • 2.  Re: CA APM Agent log4j conflict

    Posted 01-10-2016 05:00 PM

    Hi Tulio,

    It sounds like a similar problem to this KB: Failed to load the specified log manager classorg.jboss.logmanager.LogManager - seen in agent logs

    Also documented in the APM 10.0 wiki: JBoss Application Server Logging Considerations

     

    Per the first of the 2 possible solutions advised if you disable agent logging at startup by commenting this line from the IntroscopeAgent.jboss.profile & re-enable after startup does it stop the log entry flooding?

    log4j.logger.IntroscopeAgent=INFO, console, logfile

    If yes then you can then try the 2nd solution to avoid interaction after startup

     

    Thanks

     

    Lynn



  • 3.  Re: CA APM Agent log4j conflict

    Posted 01-11-2016 07:25 AM

    Hi Tulio:

    Please let know if you need further assistance

     

    Thanks

    Hal German