Why does the EUM processor fail to start with port 7003?

Not a customer? Start a free trial

Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.

Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community

Problem

The EUM processor fails to start if provided with port 7003 for the EUM processor, even though the port seems free using the following command:

netstat -an | grep 7003

The issue is due to port 7003 being used internally as the admin port. This configuration is defined in the local-eum-processor.yml file within the <EUMHome>/eum-processor/conf directory:

adminConnectors:
- type: http
port: 7003

Therefore, there will be a conflict for this port when the process is starting up. The processor will fail and show a net bind exception in the logs.

Solution

Use a different port for EUM HTTP/HTTPS other than 7003, or change the YAML configuration file to select a different port for internal use of EUM.

Cisco AppDynamics Community