I am evaluating the AppDynamics saas product and I'm seeing the following behavior:
- The agent initializes correctly and my appserver (Jetty + Jersey + HornetQ JMS) starts up
- I can see the machine in the AD dashboard
- CPU load is 0
- I make an HTTP request, which pegs one CPU core and the request never completes
- The agent stops reporting
- Thread dumps of the JVM show that AD-related threads are constantly in a RUNNABLE state.
Removing the -javaagent flag from the JVM options makes my app run correctly again. Using the ADLite agent works as expected.
Is there a way to enable some kind of local console logging for the agent to determine where it is spending time?
$ java -version
java version "1.6.0_35"
Java(TM) SE Runtime Environment (build 1.6.0_35-b10-428-11M3811)
Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01-428, mixed mode)
[INFO]: JavaAgent - Using Java Agent Version [Server Agent v3.7.5.0 GA #2013-06-24_15-31-38 r0e128d1327d0bebdf06fa72e0f1b9311694284af 3]
Hello Bob,
Can you please attach the agent logs here ? would be also great to have couple of thread dumps where you see cpu utilization is more.
I needed to increase the JVM's permgen size. It was stuck in an endless cycle of unloading and re-synthesizing classes.
Wat was default perm gen size ? In general we reocmmend 256 MB of perm gen space. Also would be great to have zipped version of agent logs as well
You can find the agent log files at <Agent_Installation_Directory>/logs. Feel free to zip up the content of the entire directory.