Connector Xpress 2.0 fails to start correctly and Tomcat closes immediately

Products

• CA Identity Suite
• CA Identity Manager

Issue/Introduction

Connector Xpress 2.0 (CX2.0) fails to initialize properly. After starting the application as administrator and initializing MongoDB, the Tomcat service starts but terminates almost immediately.

Error logs indicate that required ports are already in use, preventing the service from remaining active.

Catalina log from the Tomcat logs folder shows the following error:

SEVERE [main] org.apache.catalina.core.StandardServer.await Failed to create server shutdown socket on address [localhost] and port [8005] (base port [8005] and offset [0])

Environment

• Product: CA Identity Suite, Identity Manager
• Component: Connector Xpress 2.0
• Version: 15.x
• Operating System: Windows

Cause

A port conflict exists on TCP port 8005. This port serves as the default Apache Tomcat shutdown port. On certain Windows environments, this port is occupied by system processes or other services (such as SMS Agent Host), which prevents Connector Xpress 2.0 from binding to the port during startup.

Resolution

Change the Tomcat shutdown port to an available port number to resolve the conflict.

1. Navigate to the Connector Xpress 2.0 installation directory.
2. Locate the configuration file at \tomcat\conf\server.xml.
3. Open server.xml in a text editor.
4. Locate the line: <Server port="8005" shutdown="SHUTDOWN">.
5. Verify an alternative port (e.g., 8006 or 9005) is free by running netstat -aon | findstr 8006 in a command prompt.
6. Update the port value from 8005 to the identified empty port.
7. Save changes to server.xml.
8. Restart Connector Xpress 2.0.