Discussion Feed

Hi   We were using JBOSS 5.2 and appdynamics was working absolultely fine (with setting in run.sh).  We have recently upgraded to JBOSS v6.4 and are not able to set the agent.  We have followed all the steps to the hilt mentioned in the documentation but still havent been able to get it up and running.   I have made the entries in   standalone.conf JBOSS_MODULES_SYSTEM_PKGS="org.jboss.byteman,com.singularity,org.jboss.logmanager" JAVA_OPTS ="$JAVA_OPTS -Djava.util.logging.manager=org.jboss.logmanager.LogManager -Xbootclasspath/p:/application/dbmargin/JBoss/colline/jboss/modules/system/layers/base/org/jboss/log4j/logmanager/main/log4j-jboss-logmanager-1.1.1.Final-redhat-1.jar"   The server restarts without an issue till this point. Thereafter I make the following modification standalone.sh JAVA_OPTS="$JAVA_OPTS -javaagent:/application/dbmargin/dbAPM/ver4.1.2.2/javaagent.jar"   and I get the following error. "log4j:WARN No appenders could be found for logger (com.singularity.MissingMethodGenerator). log4j:WARN Please initialize the log4j system properly."   I have tried changing the log4j JAR to various others available on the server, but to no avail.   And the documentation doesnt mention anywhere that we need to furnish the following details, what we used to do in run.sh in JBOSS v5.x Dappdynamics.controller.hostName= Dappdynamics.controller.port= Dappdynamics.agent.applicationName="xy-za" Dappdynamics.agent.tierName=xyz Dappdynamics.agent.nodeName=xxx-yyyy Dappdynamics.agent.accountName=xxx Dappdynamics.agent.accountAccessKey=xxx Dappdynamics.controller.ssl.enabled=true   I'll be highly grateful if anyone can assist in resolving this issue?   Many Thanks D     ... View more