Hi ,
I get the message "No agent connected " in the viewer.
Logfile server agent says : Agent Compatiblity error! Agent version [Server Agent Lite v3.3.4.0 RC Build Date 2013-03-20 20:23]
I am using Weblogic 10.x with JDK Java 6-24
What could be wrong??
Tia
Peter Westerbeek
Hi Peter,
We have a know issue for the agent compatibility error, but that should not stop agent to send data to Lite Viewer.
We can see error in liteagent logs, but BT registration works fine, we had filed internal bug to resolve the compatability error:
============
[main] 26 Apr 2013 12:04:31,083 ERROR ConfigurationChannel - Agent Compatiblity error! Agent version [Server Agent Lite v3.3.4.0 RC Build Date 2013-03-20 20:23]
java.lang.IllegalStateException: This agent is not compatible with the controller version.
...
[AD Thread Pool-Global0] 26 Apr 2013 12:04:50,571 INFO BusinessTransactionRegistry - Registered BT Name[/SprintAppU/], Id[2]
===============
Can you do a screen refresh at viewer once you restart the server (with lite agent pointing to viewer host and port) and check if the messages goes. If you still see the please attached the logs under <lite_agent>/logs
Also we suggest you to post lite related queries in feature under AD lite section
http://appsphere.appdynamics.com/t5/AppDynamics-Lite/ct-p/AppDLite
Thanks,
Arun
Hi Peter,
We have a know issue for the agent compatibility error, but that should not stop agent to send data to Lite Viewer.
We can see error in liteagent logs, but BT registration works fine, we had filed internal bug to resolve the compatability error:
============
[main] 26 Apr 2013 12:04:31,083 ERROR ConfigurationChannel - Agent Compatiblity error! Agent version [Server Agent Lite v3.3.4.0 RC Build Date 2013-03-20 20:23]
java.lang.IllegalStateException: This agent is not compatible with the controller version.
...
[AD Thread Pool-Global0] 26 Apr 2013 12:04:50,571 INFO BusinessTransactionRegistry - Registered BT Name[/SprintAppU/], Id[2]
===============
Can you do a screen refresh at viewer once you restart the server (with lite agent pointing to viewer host and port) and check if the messages goes. If you still see the please attached the logs under <lite_agent>/logs
Also we suggest you to post lite related queries in feature under AD lite section
http://appsphere.appdynamics.com/t5/AppDynamics-Lite/ct-p/AppDLite
Thanks,
Arun
problem is solved. It was a wrong configutration in the registry.
Peter Westerbeek