Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

What do I do when an orchestration error appears on starting Java Agent after install?

How do I resolve post-installation orchestration errors that appear when I restart Java Agent?

This article outlines the symptoms, cause, and solution for an orchestration error that appears when re-starting a Java Agent after installation.

 

Table of Contents

Symptoms

Diagnosis

Solution

Resource Summary

 

Symptoms

After installing a Java agent, a customer saw an error in the Java agent log when starting their application:

 

[Cloud Instance IP Address Resolver] 30 Oct 2019 14:35:26,586 ERROR XMLConfigManager - Fatal transport error while connecting to URL [http://169.254.169.254/latest/meta-data/public-hostname:] org.apache.http.conn.ConnectTimeoutException: Connect to 169.254.169.254:80 [/169.254.169.254] failed: connect timed out[Cloud Instance IP Address Resolver] 30 Oct 2019 14:35:26,586 INFO XMLConfigManager - Cloud Instance IP Address Resolver could not reach cloud instance data web service

 

[AWS Agent Resolver] 30 Oct 2019 14:35:26,590 ERROR XMLConfigManager - Fatal transport error while connecting to URL [http://169.254.169.254/latest/user-data:] org.apache.http.conn.ConnectTimeoutException: Connect to 169.254.169.254:80 [/169.254.169.254] failed: connect timed out[AWS Agent Resolver] 30 Oct 2019 14:35:26,590 INFO XMLConfigManager - AWS Agent Resolver could not reach cloud instance data web service

[AWS Agent Resolver] 30 Oct 2019 14:35:26,590 INFO XMLConfigManager - AWS Agent Resolver did not find valid agent resolution info [null][Cloud Instance IP Address Resolver] 30 Oct 2019 14:35:36,598 ERROR XMLConfigManager - Fatal transport error while connecting to URL [http://169.254.169.254/latest/meta-data/local-ipv4:] org.apache.http.conn.ConnectTimeoutException: Connect to 169.254.169.254:80 [/169.254.169.254] failed: connect timed out

 

[Cloud Instance IP Address Resolver] 30 Oct 2019 14:35:36,598 INFO XMLConfigManager - Cloud Instance IP Address Resolver could not reach cloud instance data web service[Cloud Instance IP Address Resolver] 30 Oct 2019 14:35:46,601 ERROR XMLConfigManager - Fatal transport error while connecting to URL [http://169.254.169.254/latest/meta-data/public-ipv4:] org.apache.http.conn.ConnectTimeoutException: Connect to 169.254.169.254:80 [/169.254.169.254] failed: connect timed out

 

Diagnosis

During their agent installation, the customer had accidentally enabled the orchestration option in the configuration. 

 

By default, the configuration orchestration option assumes that the agent is hosted on AWS and tries to find its hostname from the AWS discovery services. When the agent is not running on AWS, it produces the above messages. 

 

Solution

This can be corrected by correctly setting the enable-orchestration flag to false as per the Java Agent Configuration Properties documentation, which states:

 

Other Properties: Enable Orchestration

When set to true, enables auto-detection of the controller host and port when the app server is a compute cloud instance created by an AppDynamics orchestration workflow. See Controller Host Property and Controller Port Property.

 

In a cloud compute environment, auto-detection is necessary for the Create Machine tasks in the workflow to run correctly.

 

If the host machine on which this agent resides is not created through AppDynamics workflow orchestration, this property should be set to false.

 

Element in controller-info.xml:  <enable-orchestration>

Type: Boolean

Default: False

Required: No

 

Resource Summary

Java Agent Configuration Properties

Version history
Revision #:
6 of 6
Last update:
3 weeks ago
Updated by:
 
Labels (1)


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