Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

Why does my application take longer to start-up after adding an Appdynamics Agent?

Question

 

Why does my application take longer to start-up after adding an Appdynamics Agent? How do I resolve this?

 

Answer

 

If there is a delay in application start-up time after adding the agent, then it can be due to the Agent requesting configuration details from the JVM.

 

By default, the Agent reserves 60 seconds to get a response from the Controller and start the instrumentation process. In some cases, it takes longer to get a response which causes the delay.

 

Change the following system property to 3 seconds, and the instrumentation request will be issued in parallel with application startup. Changing the parameter will have no impact on the application.

 

 

While running the agent, add the following system property to the Agent configuration:

-Dappagent.start.timeout=3

 

Example:  

java -Dappagent.start.timeout=3 -javaagent:<AgentInstallDir>/verx.x.x/javaagent.jar
 

 

Version history
Revision #:
5 of 5
Last update:
‎10-04-2018 03:43 PM
Updated by:
 
Labels (1)
Tags (1)


Found this article helpful? Click the Thumbs Up button.
Have an additional comment? Post it below.
0 Kudos
Comments

We've tried adding the timeout=3 in the java option but it increased the time instead of decrease.  Is there another was of achieving a quicker response time?

@Richard.Walls, it looks like more investigation is needed to resolve the specific response time issue you're experiencing. I spoke with @Rajendra.Nautiyal, and his feeling is that further troubleshooting will take a thorough log file review—which makes your question more suited to opening a Support ticket.

 

Thank you for bringing the conversation to the Community! If you discover a shareable cause, please don't hesitate to post. 

 

Claudia Landivar

Community Manager & Editor