Apologies for the delay in our reply!
I checked with our support team, and it looks like you're doing all the things we recommend. Suggest opening a support case.
Thanks,
Cody
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
Hi Deepak,
Could you file a support case with details listed here
1) Zipped agent logs
2) Server stdout logs
3) Server startup scripts where ever you have added java agent configurations.
Thanks
Rajesh
The ref ticket with AppD - #89269
ALthough this must have come from internal support team, and you may not see my name. But this incidednt and I are talking about the same incident. Just because there was a delay in getting it fixed from internal support team, I had to resign to public forum to get the resolution.
Server logs, agent logs & conf files are attached with the request.
Please do let me know if you need any more details.
Many Thanks
Deepak
Hi Deepak,
I have sent the GTM invite on ticket. Please join the GTM.
Thanks
Rajesh
