AppD Archive

AppDynamic Lite Server Agent installation Issue with Virgo Jetty Server

CommunityUser
Splunk Employee
Splunk Employee

     I am trying to install AppDynamics Lite Server and viewer versions on my machine inorder to check the performance of the code and time taking for executions. As per the instructions  I have edited startup.bat file of server(VIRGO JETTY SERVER) to include JAVA_OPTS(SET JAVA_OPTIONS=%JAVA_OPTIONS% -javaagent:\C:\Users\GPra\Desktop\profilers\AppDynamicsLite\AppDynamicsLite\AppServerAgentLite\javaagent.jar) and restarted the server for changes as part of agent .We have also installed LiteViewer and able to see the console as shown below, but it is showing as no agents connected .Kindly requesting to help to have agent connection enabled.

                We have done following changes as part of connecting agent server and lite viewer..

àset JAVA_OPTS in startup.bat of Virgo Jetty Server we are using.

àset org.osgi.framework.bootdelegation=com.singularity.* property inside org.eclipse.virgo.kernel.launch.properties file of kernel for virgo(inside lib)

à Extract the Viewer files from the LiteViewer.zip file

à Go the directory where you extracted the LiteViewer.zip file

à Run the adlite-viewer.jar using the Java interpreter(java -jar adlite-viewer.jar)

àRestart of the server(Virgo jetty server)

                After this I am able to open browser and below is attached screenshot for same, but seen  no agents connected and also I didn’t find any log file generated inside logs of AppServerAgentLite.

                Please Help in getting agents to run in viewer.

                Please let me know if any other additional information is required.

0 Karma

Arun_Dasetty
Super Champion

Hi Praneeth,

please be sure that we do not see Virgo Jetty Server listed in supported servers list as per docs, however if virgo jetty server runs on jvm we should be able to start server with liteagent and get some visisbility of BT here. Can you confirm whether the machine on which jetty server/liteagent is installed and liteviwer is installed is on the same machine, if this is not the case, make sure that liteviwer host is reachable from liteagent machine host.

Ex: If this is the case: open shell prompt and check if "telenet 192.168.1.4 8990" command succeeds from lite agent machine2 ip 192.168.10.2:

Machine1-ip 192.168.1.4 is used to install liteviewer (http://localhost:8990)

Machine2-ip 192.168.10.2 is used to install jetty server with lite agent

We request you to restart jettery wtih lite agent in addition to -javaagegnt param as follows:

-Dappdynamics.viewer.host=192.168.1.4 -Dappdynamics.viewer.port=8990 -javaagent:<liteagent_dir>/javaagent.jar in jetty startup script

Can you please provide jetty startup script file and console output while starting jetty with lite agent, if the issue still persists

Thanks,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Kumar,
Thanks for the reply.We have been using Virgo jetty server and LiteViewer/LiteAgent in same machine.

I have also attached the script to startup virgo jetty server and below is the console output . Could you please suggest any resolution .Thanks in Advance

[cid:image001.png@01CEEF1B.D0482EB0]

[cid:image002.png@01CEEF1B.D0482EB0]

Thanks and Regards,
Praneeth G


0 Karma

Arun_Dasetty
Super Champion

Hi Praneeth,

We could not locate any agent related startup logs in provided screenshots. Can you please provide the following logs:

- server script file or config file in which you have added -javaaegnt:<liteagent_dir>/javaagent.jar entry

- start the server and redirect the entire console output to log file and send it Or you can send the server console.log itself on which you have configured liteagent

Keep us posted the requested information to assist you better

Thanks,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Team,

     Please find required files in zip .Also just for information I am not able to see any logs inside agent C:\Users\GPra\Desktop\profilers\AppDynamicsLite\AppDynamicsLite\AppServerAgentLite\logs

startup.bat(virgo server log)

log.log(Virgo Server log)

liteviewer.log(LiteViewer log)

Please suggest if any other information is required or I am missing any information to provide

Thanks..

0 Karma

Arun_Dasetty
Super Champion

Hi Praneeth,

Can you try the attached startup.bat (rename startup.bat.txt to startup.bat) file and try if that helps, Also please make sure you do not disable agent from liteviewer UI intermetitenly as we see the following logs in ltieviewer.log:

[btpool0-4] 29 Nov 2013 07:48:31,633  INFO [btpool0-4] ApplicationManager - Disabling Agent

If the above changes did not help after restart send the dmk.bat file as well in addition to startup.bat file, we would like to see if how JAVA_OPTS is used in dmk.bat file o

Thanks,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Arun,

  I have replaced the startup.bat file provided but doesnt helped me any more still my viewer is showing no agents connected .Below is the console of viewer(pasted)

[main] 03 Dec 2013 06:05:55,610  INFO [main] AgentHandlerServlet - *****************************************************************
[main] 03 Dec 2013 06:05:55,610  INFO [main] AgentHandlerServlet - Starting  ....AppDynamics Lite Viewer 2.1.1 GA Build Date 2012-08-05 21:13:55
[main] 03 Dec 2013 06:05:55,797  INFO [main] o - Read user registration. Registration complete: [true]
[main] 03 Dec 2013 06:05:55,813  INFO [main] LiteAlertManager - Initialized Data Directory [C:\Users\GPra\Desktop\profilers\others\AppDynamicsLite\AppDynamicsLite\LiteViewer]
[main] 03 Dec 2013 06:05:55,813  INFO [main] LiteAlertManager - Creating alert: Default ART Alert
[main] 03 Dec 2013 06:05:55,813  INFO [main] LiteAlertManager - Creating alert: Default Errors/min. Alert
[main] 03 Dec 2013 06:05:55,813  INFO [main] LiteAlertManager - Alerts already exist or were created in the past; defaults will not be created.
[main] 03 Dec 2013 06:05:55,813  INFO [main] DirectoryResolver - Deleting directory [C:\Users\GPra\Desktop\profilers\others\AppDynamicsLite\AppDynamicsLite\LiteViewer\data]

Also I see no agent disabled log in viewer logs pasted above,Could you please let me know where we can enable agent from liteviewer UI .

Here dmk.bat and startup.bat are attachements from virgo server and liteviwer.log is log of viewer(placed inside zip). Please suggest me how to proceed further.

0 Karma

Arun_Dasetty
Super Champion

Hi Praneeth,

We see that Monitoring button in liteviewer UI is enabled "ON" and we could confirm that agent is enabled from the screenshots attached in initial post.

Can you take a backup of startup.bat and dmk.bat and replace the files with attached dmk.bat and startup.bat files and restart  server and see how it goes.

we have added the following entry in attached files:

SET JAVA_OPTS=%JAVA_OPTS% -javaagent:"C:\Users\GPra\Desktop\profilers\AppDynamicsLite\AppDynamicsLite\AppServerAgentLite\javaagent.jar"

Thanks,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Team,

        Thanks for the reply,With the changes mentined earlier I am able to start agent and lite viewer successfully and able to see logs .

       But now I am getting below exception in logs

main] 09 Dec 2013 02:06:19,799  INFO BTEventProcessor - Scheduled BT Event Processor
[main] 09 Dec 2013 02:06:19,799  INFO SlowAndStallRequestMonitor - Stall Request checker setup
[main] 09 Dec 2013 02:06:19,799  INFO SlowAndStallRequestMonitor - Slow Request checker setup to check for requests slower than 300 ms, at interval 300 ms.
[main] 09 Dec 2013 02:06:19,815  INFO Java16AgentService - retransformClass for java16 called!
[main] 09 Dec 2013 02:06:19,862  INFO Java16AgentService - Retransformed class [[class java.util.logging.Logger]]
[main] 09 Dec 2013 02:06:19,862  INFO LoggerRuleApplier - Log4j and JDK logger rules applied
[main] 09 Dec 2013 02:06:19,877  INFO ErrorRegistry - Error Registry initialized
[main] 09 Dec 2013 02:06:19,877  INFO TransactionMonitor - Applying 'slow-request-threshold', '500'
[main] 09 Dec 2013 02:06:19,877  INFO SlowAndStallRequestMonitor - Slow Request checker setup to check for requests slower than 500 ms, at interval 500 ms.
[main] 09 Dec 2013 02:06:19,877  INFO TransactionMonitor - Applying 'enable-transaction-correlation', 'false'
[main] 09 Dec 2013 02:06:19,877  INFO TransactionMonitor - Transaction correlation is disabled for node. Incoming request headers will not be read to check for continuing transaction
[main] 09 Dec 2013 02:06:19,909 ERROR ForkingThreadRuleApplier - configure was not called before start!
[main] 09 Dec 2013 02:06:19,909  INFO LifeCycleManager - Started service [TransactionMonitoringService]
[main] 09 Dec 2013 02:06:19,909  INFO ConfigurationChannel - Sending Registration request with: Application Name [Server App], Tier Name [Server Tier], Node Name [Server Node], Host Name [GPRA-V] Node Unique Local ID [Server Node], Version [Server Agent Lite v3.3.4.0 RC Build Date 2013-03-20 20:23]
[main] 09 Dec 2013 02:06:20,002  INFO ConfigurationChannel - Auto agent registration attempted: Application Name [Server App] Component Name [Server Tier] Node Name [Server Node]
[main] 09 Dec 2013 02:06:20,002  INFO ConfigurationChannel - Auto agent registration SUCCEEDED!
[main] 09 Dec 2013 02:06:20,002  INFO ConfigurationChannel - Registration information received Node ID[1] Component ID[1] Application ID [1]
[main] 09 Dec 2013 02:06:20,034  INFO ConfigurationChannel - Controller version [0.0.0]
[main] 09 Dec 2013 02:06:20,034 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.
 at com.singularity.ee.agent.appagent.kernel.config.xml.o.a(o.java:739)
 at com.singularity.ee.agent.appagent.kernel.config.xml.q.a(q.java:470)
 at com.singularity.ee.agent.appagent.kernel.config.xml.s.a(s.java:454)
 at com.singularity.ee.agent.appagent.kernel.config.xml.l.a(l.java:283)
 at com.singularity.ee.agent.appagent.kernel.config.xml.ab.run(ab.java:443)
 at com.singularity.ee.agent.appagent.kernel.config.xml.e.a(e.java:184)
 at com.singularity.ee.agent.appagent.kernel.b.h(b.java:112)
 at com.singularity.ee.agent.appagent.kernel.JavaAgent.initialize(JavaAgent.java:116)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at com.singularity.ee.agent.appagent.AgentEntryPoint.premain(AgentEntryPoint.java:153)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:597)
 at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:323)
 at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338)
[main] 09 Dec 2013 02:06:20,034  INFO AgentConfigWatchdog - Received properties from controller, going to refresh.
[main] 09 Dec 2013 02:06:20,034  INFO ConfigurationChannel - Setting disable-agent to false
[main] 09 Dec 2013 02:06:20,034  INFO KernelProperties - Kernel property='disable-agent', old value='null', new value='false' notified to 'com.singularity.ee.agent.appagent.kernel.config.xml.l'
[main] 09 Dec 2013 02:06:20,034  INFO AgentConfigWatchdog - ************ Started applying service properties from controller ***************
[main] 09 Dec 2013 02:06:20,034  INFO TransactionMonitor - Applying 'max-business-transactions', '30'
[main] 09 Dec 2013 02:06:20,034  INFO TransactionMonitor - Agent will identify a maximum of [30] business transactions.
[main] 09 Dec 2013 02:06:20,034  INFO AgentConfigWatchdog - ------------ Finished applying service properties from controller ---------------

Could you please let us know is Server(Virgo Jetty Server) which we are using is not compatible with AppDynamics if not please suggest how to proceed ..

Thanks in Advance...

0 Karma

Arun_Dasetty
Super Champion

Hi Praneeth,

We understood that you are referring to following error in liteagent logs:

=======================

[main] 09 Dec 2013 02:06:20,034 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.
 at com.singularity.ee.agent.appagent.kernel.config.xm

l.o.a(o.java:739)

=======================

We see this is a known issue in lite agent and we confirm that your lite agent is compatable with lite viwer and you can ignore this error message in agent logs and this error will not affect lite agent reporting metrics to liteviwer UI.

Hope that clarifies.

Thanks,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Arun,

         Thanks for the information.After starting server,Virgo services which are running earlier are not starting now but agent is getting started .Also no error messages in virgo server log.Services which we are using are OSGI serviceswhich woks with AMQ Connections .Can you suggest any thing on this.

Thanks and Regards,

          Praneeth

0 Karma

Arun_Dasetty
Super Champion

Hi Praneeth,

It is strange and we do not expect such behavior, Can you please send the server console logs while starting with agent and server failed to start, we understood that you do not fine any errors, but we would like to see if any logs helps here.

Please send the liteagent logs and also 5-6 thread dumps collected with 15-20 secs period gap when server failed to start with lite agent started fine to debug further.

Thanks.

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Arun,

     Please find the required files in zip.I have attached local virgo log,liteviewer log,3 instances of agent logs.

     Please let me know if any additional information is required.

Thanks in Advance...

0 Karma

Arun_Dasetty
Super Champion

Hi Praneeth,

We understood that server fails to start after the following errors raised in virgo server.log let us know if any disconnect:

======================

    Line 2667: Caused by: org.eclipse.virgo.kernel.osgi.framework.ExtendedClassNotFoundException: com.singularity.ee.agent.appagent.entrypoint.bciengine.MethodExecutionEnvironment in KernelBundleClassLoader: [bundle=com.moodys.msp.core.qpid-client_0.14.0.rh3]
    Line 2671: Caused by: java.lang.ClassNotFoundException: com.singularity.ee.agent.appagent.entrypoint.bciengine.MethodExecutionEnvironment
    Line 2686: Caused by: org.eclipse.virgo.kernel.osgi.framework.ExtendedClassNotFoundException: com.singularity.ee.agent.appagent.entrypoint.bciengine.MethodExecutionEnvironment in KernelBundleClassLoader: [bundle=com.moodys.msp.core.qpid-client_0.14.0.rh3]
    Line 2690: Caused by: java.lang.ClassNotFoundException: com.singularity.ee.agent.appagent.entrypoint.bciengine.MethodExecutionEnvironment

====================

we see tthe MethodExecutionEnvironment class exists in <liteagent_dir>/javaagent.jar , can you check the integrity of the liteagent and let us know if installing lite agent afresh helps here, we suspect the corrupted liteagent could be causing an issue here, let us know if any disconnect in our understanding.

If the above said is not the case, can you please try the following:

- click "Monitoring" button liteviwer UI (http://localhost:8990) to disable lite agent and restart the virgo server with lite agent configured and see if the server starts fine

- If the above step does not help , can you try the attached lite agent and see how it goes

If the issue still persists, please send the latest virgo server log.log and also attach the thread dumps as we requested earlier to debug further.

Thanks,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Team,

      Sorry for late reply,
I have taken new Agent lite attached and tried but I am facing same issue.I am attaching latest attached logs required.Please suggest.

In Virgo server logs I am getting same exception

(caused by: org.eclipse.virgo.kernel.osgi.framework.ExtendedCl

assNotFoundException: com.singularity.ee.agent.appagent.entrypoint.bciengine.MethodExecutionEnvironment in KernelBundleClassLoader: [bundle=com.moodys.msp.core.qpid-client_0.14.0.rh3])

mentioned by your team earlier please suggest what might be the reason for the same.Suggest me how to check the integrity of LiteAgent installation.

Please let meknow any additional information is required

0 Karma

Arun_Dasetty
Super Champion

Hi Praneeth,

Can you please try the following:

- take a backup of existing lite agent install directory

- remove all files under lite agent directory, use the lite agent archive attached and restart the liteviwer and then restart virgo server and see how it goes

- if the issue still persists , can you add the following jars and jars under directories javaagent.jar and lib/  and lib/tp/ to the classpath specifically and restart virgo server and let us know how it goes.

To set the expectations right, please be sure this could be be support issue as we said Lite agent offcially do not supoort Virgo server, we would like to try few things and see if that helps.

Thanks,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Team,

Below are the required files attached,Please suggest If I am missing still something,here I am not able to see any log for agent.

Thanks...

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...