DX APM : apmia-wrapper Vs Apache port usage issue
search cancel

DX APM : apmia-wrapper Vs Apache port usage issue

book

Article ID: 372095

calendar_today

Updated On:

Products

CA Application Performance Management (APM / Wily / Introscope)

Issue/Introduction

 Noticed that when the APMIA Agent is up,  the wrapper occupies the same port as Apache. 

Environment

On Prem 24.1 

Cause

Port Conflict 

Resolution

APMIA wrapper port, basically, by default, the HTTP Collector runs on port 8085. Ensure that the port is available for HTTP Collector.

If the port is unavailable, 

 

Workaround #1:

 

Change the port for HTTP Collector in the APM Command Center.

 

Workaround #2:

 

Change the Tomcat shutdown port number from 8085 to a non-used port

 

Workaround #3: 

 

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-collect