ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

DX APM - Infrastructure Agent Stops Tomcat Service on SDM Server if started with default port 8085

book

Article ID: 238081

calendar_today

Updated On:

Products

DX Application Performance Management

Issue/Introduction

Symptoms:
DX APM Infrastructure Agent downloaded from SaaS as APMIA Agent in the latest version 22.1.0.25. This Infrastructure Agent is installed on a Server running already the CA Service Management Server SDM 17.3 installed before. The Tomcat Shutdown Port in SDM is 8085. When the CA Infrastructure Agent Service is started the SDM Tomcat shuts down.

Cause

This problem is related to the defect DE531944 & CGR US813039. The default configuration of the Infrastructure Agent has the http-collector configured by default and this is using Port 8085 overlapping with the default Tomcat Shutdown Port of CA SDM 17.3.

CA SDM Tomcat | Tomcat Shutdown Port: 8085


https://techdocs.broadcom.com/us/en/ca-enterprise-software/business-management/ca-service-management/17-3/installing/installation-prerequisites/supported-ports-and-port-ranges.html

HTTP Collector Ingress Resource Creation
          backend:
            serviceName: apmia-http-collector-web
            servicePort: 8085

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-apm-saas/SaaS/implementing-agents/Universal-Monitoring-Agent/UMA-for-HTTP-Collector/HTTP-Collector-Ingress-Resource-Creation.html

Environment

Windows Server 2019
CA Service Management Server SDM 17.3- already installed before
DX APM Infrastructure Agent 22.1.0.25 - being installed as a 2nd instance of the APMIA on the same machine

Resolution

To be fixed in a future release of DX APM SaaS AMPIA Agent.

WORKAROUND #1:

Change the Tomcat shutdown port number from 8085 to a non-used port. Below is the SDM doc link on port configuration:

https://techdocs.broadcom.com/us/en/ca-enterprise-software/business-management/ca-service-management/17-3/administering/configure-ca-service-desk-manager/configure-ca-sdm-and-the-components/server-configuration-utility.html

 

WORKAROUND #2:

Deactivate the http-collector in the extensions/Extensions.profile file by commenting in the line below as you can see on the screenshot. 

#introscope.agent.extensions.bundles.boot.load=http-collector-dd040621xt13-2022.1.0.25

 

IMPORTANT NOTE: The http collector extension can be disabled only if no NodeJS monitoring is required.

 

WORKAROUND #3:

Alternatively, you can change the default port "8085" of the http-collector extension via ACC(APM Command Center). ACC (APM Command Center) option will be available in the DX-APM SaaS

APM Command Center: To change the http-collector extension default port.

DX-APM -> Settings (Left pane) -> APM Command Center

For more information on ACC, please refer to the tech doc: 

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-apm-saas/SaaS/implementing-agents/deploy-agent-packages-using-apm-command-center.html 

 

WORKAROUND #4:

In case the nodejs monitoring is needed, you can alternatively change only the http-collector port in the bundles.properties file. Http-collector port 8085 can be set to any free port on the server and there are no restrictions to that. It's just a listening port so the only requirement is to configure whatever probe is sending the data in to get to the correct port.

Additional Information

You can use the following command to install and uninstall your APMIA instance:

APMIACtrl.bat install service_name "<service_name>" display_name "<display_name>"
APMIACtrl.bat uninstall service_name "<service_name>" display_name "<display_name>"

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-apm-saas/SaaS/implementing-agents/infrastructure-agent/Install-the-Infrastructure-Agent-on-Windows.html

Question #1 What is http-collector?

Answer: The http-collector is a collector agent where probes like nodejs can communicate with the protocol HTTP/HTTP(s). It is part of APMIA. The probes were connected using ARF protocol and there is still backward compatibility which means probes can still connect to APMIA using ARF. The HTTP protocol supports the scale of collector-agents/APMIA and it can have an external load balancer where 100/1000 probes can connect to APMIA without having knowledge of APMIA where it connects. 

Background: ARF protocol has a limitation of accepting 15 probes per APMIA and it cannot work with std load balancers hence configuration at probes becomes quite difficult in pointing 15 sets of probes to one APMIA. The HTTP protocol can address these limitations.

Tech docs:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-apm-saas/SaaS/implementing-agents/Universal-Monitoring-Agent/UMA-for-HTTP-Collector.html
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/dx-apm-saas/SaaS/implementing-agents/infrastructure-agent.html

Question #2: Can this interface be used to receive data as far as there is already a REST interface in EPAgent / APMIA that is used to receive metrics and transaction trace data?

Answer: EPAgent still exists. Yes, REST APIs are available with Http-Collector and they are more compatible with the probe's ARF(Agent Remote Function) messages. It also needs tracers at APMIA like extensions NodeExtension, PHPExtension, etc... for Function Call and Returns messages. It can have another agent (Hostname|Process|Agent) for each probe (whereas EPAgent reports metrics in the same APMIA).  

Question #3 Which probes does the new collector already support and/or is intended to support in the future?

Answer: Presently, only supported for Nodejs and yes, there was a feature plan to migrate for other probes (Python, PHP, etc...) from ARF to HTTP. However, for the moment we do not have any timeline fixed for any other probes than Nodejs.

Attachments