It usually has something to do with permissions or ownership of the binaries and logs. Is there a service id that runs the java instance? Is it part of the linux/unix group that owns the appdynamics binaries? What do you see in the appagent logs? If ...
This is not an Appdynamics issue. Our Customer migrated from using linux jboss to linux Tomcat. Their application did not have memory issues when running on jboss, but now that they have migrated over to Tomcat they are having memory problems. I was ...
Install normal java agent. Also for Jenkins you can configure the Mbeans after you start receiving Jenkins data from the application.This should get you started.https://docs.appdynamics.com/display/PRO45/Monitor+JMX