Hi,
I'm new to AppDynamics. I've installed AppDynamics lite and followed the below forum to configure javaagent on my Linux machine.
http://litedocs.appdynamics.com/display/ADLite/JBoss
Our application is running on Jboss and i've added javaagent.jar into run.sh.
export JAVA_OPTS="$JAVA_OPTS -javaagent:/home/AppDynamicsLite/AppDynamicsLite/AppServerAgentLite/javaagent.jar"
and restarted lite and my app server . It's still saying no agent connected.
Thanks,
YOgesh
Hi Yogesh,
We see such issues in the following cases:
- if you have started liteagent/jboss first and later you started liteviewer we might see such issue, we request you to start liteviwer and then start jboss(with liteagent)
- can you do browser refresh and see if that makes any difference in liteviewer ui
- physical machine on which you installed liteagent is running on machine1 and liteviwer is running on machine2 and machine1 could not ping to machine2, if this is the case, please make sure you could ping successfully machine2 from machine1 in shell prompt and then restart jboss server with liteagent in addition to -javaagent arg with following -D jvm args added -Dappdynamics.viewer.host=liteviwerhostip -Dappdynamics.viewer.port=liteviewerport
- also make sure there is no firewal rules added that blocks liteagent to connect to liteviwer port running on other machine
Let us know if that information helps.
Thanks,
Arun
Hi Arun,
Thanks for replying. I've installed liteviewer on the same host where my application is installed.
I did add the hostip also in run.sh of jboss and restarted app server. I did start my app server after starting liteviewer.
There are no firewall enabled.
Browser refresh also not helping me in that case.
Thanks,
YOgesh
[main] 10 Dec 2013 07:45:03,598 INFO [main] AgentHandlerServlet - *****************************************************************
[main] 10 Dec 2013 07:45:03,609 INFO [main] AgentHandlerServlet - Starting ....AppDynamics Lite Viewer 2.1.1 GA Build Date 2012-08-05 21:13:55
[main] 10 Dec 2013 07:45:04,173 INFO [main] o - Read user registration. Registration complete: [true]
[main] 10 Dec 2013 07:45:04,319 INFO [main] LiteAlertManager - Initialized Data Directory [/home/AppDynamicsLite/AppDynamicsLite]
[main] 10 Dec 2013 07:45:04,329 INFO [main] LiteAlertManager - Creating alert: Default ART Alert
[main] 10 Dec 2013 07:45:04,330 INFO [main] LiteAlertManager - Creating alert: Default Errors/min. Alert
[main] 10 Dec 2013 07:45:04,330 INFO [main] LiteAlertManager - Alerts already exist or were created in the past; defaults will not be created.
[main] 10 Dec 2013 07:45:04,331 INFO [main] DirectoryResolver - Deleting directory [/home/AppDynamicsLite/AppDynamicsLite/data]
pwd
/home/AppDynamicsLite/AppDynamicsLite/AppServerAgentLite/logs
ls
retrun nothing
Hi Yogesh,
Unfortunately the provided information does not help. Can you please send the following to assist you faster:
- jboss startup script file in which you configured -javaagent entry (ex: run.sh, domain.sh etc)
- jboss startup command you used to start jboss server (ex: cmd> <JBOSS_DIR>/bin/run.bat )
- console output while starting jboss server with liteagent (ex: send the output.log when you start as follows:
cmd> <JBOSS_DIR>/bin/run.bat >> output.log
- we understood that you have changed the LiteViewer directory name to AppDynamicsLite, can you confirm the jboss server version details?
Please keep us posted the requested information, we suspect either liteagent directory permisison issues, or wrong path, or wrong location of -javagent entry in jboss startup script here.
Thanks,
Arun
Hi Yogesh,
Can you add the following line :
export JAVA_OPTS="$JAVA_OPTS -javaagent:/home/AppDynamicsLite/AppDynamicsLite/AppServerAgentLite/javaagent.jar"
before the line in run.sh
# Setup the java endorsed dirs
and stop the jboss and start using
shell> cd <jboss_dir>/bin
shell> ./run.sh start > output.log
send the output.log or the console output when you started run.sh command in shell prompt, if the issue still persists
Thanks,
Arun
Hi Yogesh,
Glad to hear that finally agent connected fine, From error1.png it is clear that agent regisered fine and Business transaction registerd fine as well as you noticed, Can you please confirm whether you generate load on some servlets, struts or spring or EJB transactions , please be sure that entry and auto discovery checkboxed for the corresponding request types are enabled under Configure -> transaction detection screen in liteviwer while you are making load on browser on jboss server for servlet/struts/ejb transactions.
When you say that old agent is showing up when you start jboss as service, please be sure that
once liteviwer instance can only monitor one liteagent/jvm instance.
Can you generate load on FolderServiceBean.cleanUp method and check whether load discovreed in liteviwer UI after screen refresh.
Thanks,
Arun
Hi Yogesh,
We see disconnect here, we could clearly see Business transaction registered in attached screenshot.
Also please be sure that one liteviwer instance can only monitor one jvm (one jboss instance) if you start multiple jboss instances then the first instance started will only send data and you might feel that jvm is registered in liteviwer but load on second instance is not discovered, hope that clarifies the product behavior.
Please send the latest screenshots and agent logs if there is any disconnect.
Thanks,
Arun
Hi Arun,
I'm running one isntances of jboss only. What i was telling is, we don't restart jboss using run.sh manually. We do have service called jboss which does the restart of jboss so that i can close the session and services will be running in background.One more thing, if i start service manually, our app doesnot come up.
So i had to start service using jboss not via run.sh manually and when i start service using jboss, i don't see any transaction happening with liteviewer and jvm.
Also is there any way i can run the adliteviewer in background otherwise i need to keep the session open to see the transaction happening on ui.
Thanks,
Yogesh
Hi Yogesh,
We understood that you had made sure that jboss instance is not running before you restart jboss as service, if this is the case, please let us know whether you see no agents connected before starting jboss service and you no agents connected message gone after starting jboss service but no load BT got discovered if this is the case, please send the agent lite logs collected when jboss service started with liteagent, we would like to see whether entry interceptors applied or not. in logs, also make sure load is applied on jboss and the corresponding entry point is enabled under configure -> transaction detction
regarding other query, currently we do not support starting liteviwer as service , however you create script/batch file with command and add the batch/script file in /etc/init.d or /etc/init.d/rc.local Or you can use http://upstart.ubuntu.com/ utility:
#!/bin/sh
java -jar <liteviwer_dir>/adlite-viwer.jar
Thanks,
Arun