I installed AppDynamics lite java version on my jboss-4.0.5.GA (on a windows machine) in which i deployed and running a java web app which uisng struts, spring core, ejb. App will connect to Oracle DB.
Installation of java agent & viewer in successful.
I have the viewer host & port conf configured in my run.bat.
java -javaagent:C:/Users/Pradeep/Downloads/AppDynamicsLite/AppDynamicsLite/AppServerAgentLite/javaagent.jar set JAVA_OPTS=%JAVA_OPTS% -Dappdynamics.viewer.host=localhost -Dappdynamics.viewer.port=8990
Agent log file in my appDynamicslite install dir shows. as "JavaAgent - Started AppDynamics Java Agent Successfully."
View shows that monitoring is on.
I ensured that transaction monitoring is enabled for the components that my app is using.
There is definty load on the application.
But still the flowmap is not populated properly. I could see only one node as standalone JVM. Also the viewer popped with message that either java agent is not configured or wrong transaction..
Whats went wrong in my case. Any help is really appreciated.
attaching the log files for your ref.
Thanks,
Pradeep
Hi Pradeep,
We do not see any suspicious info in logs and also we see the logs for only 2 minutes which is too short did the jvm running for more than 5 mts atleast? and did you configure lite agent on jboss server as per docs http://litedocs.appdynamics.com/display/ADLite/JBoss
Also we do not see any interceptors applied in BCT.logs we suspect the reason could be short jvm runtime, can you please make sure jboss is running for alteast 5-10 minutes and make load and see if that helps.
please be sure one lite viewer instance can only monitor one lite agent instance only.
Can you please try the following:
- stop the liteviewer and jboss server with liteagent configured
- start the liteviewer and then start jboss server
- check whether servlet, ejb, struts entry points are enabled under configure -> transaction detection screen in liteviewer
- generate load on jboss server through browser using some servlet / struts requests and see how it goes.
If the issue still persists, Can you send the following to assist you better:
- <liteviwer_install_dir>/logs and <liteviwer_install_dir>/configuration.xml file
- latest lite agent logs
Thanks,
Arun