Docker Agent Connects over Port 80 despite being Configured for HTTPS.

Products

• CA Application Performance Management Agent (APM / Wily / Introscope)
• INTROSCOPE

Issue/Introduction

     An APM 10.5.x Docker Agent has been configured to connect to the Enterprise Manager's REST API using HTTPS by specifying the following in the docker.properties file:

apm.accesstoken=<token>
apm.atc.resthttps=https://<host>:<port>/apm/appmap/graph/vertex/

Despite this configuration, the Docker Agent attempts to establish an HTTP connection. The following error is logged:

[ERROR] [com.ca.apm.microservices.docker.DecorateAgentNodes] com.wily.isengard.messageprimitives.ConnectionException: HttpHostConnectException: Connect to <host>:80 [Host/<IP Address>] failed: Connection refused: connect
 at com.wily.introscope.spec.server.appmap.remotehttp.RemoteHttpCallClient$Wrapper.call(RemoteHttpCallClient.java:120)
 at com.wily.introscope.spec.server.appmap.remotehttp.RemoteHttpCallClient.doPost(RemoteHttpCallClient.java:191)
 at com.wily.introscope.spec.server.appmap.remotehttp.RemoteHttpCallClient.doPost(RemoteHttpCallClient.java:170)
 at com.ca.apm.microservices.docker.DecorateAgentNodes$1.getAtcJSONData(DecorateAgentNodes.java:163)
 at com.ca.apm.microservices.docker.DecorateAgentNodes$1.getAtcNodeInfo(DecorateAgentNodes.java:96)
 at com.ca.apm.microservices.docker.DecorateAgentNodes$1.run(DecorateAgentNodes.java:88)
 at java.lang.Thread.run(Thread.java:745)

Environment

This issue affects 10.5.x APM Docker Agents connecting to APM 10.5.x Enterprise Managers.

Resolution

     This issue is caused by a bug on the Enterprise Manage side. To correct, request the latest Enterprise Manager hot fix available. In APM 10.5.2, this issue is addressed in Hotfix 4 and higher.

Additional Information