Java Connector Server service running but Connector port (20411) not listening in Symantec Identity Manager
search cancel

Java Connector Server service running but Connector port (20411) not listening in Symantec Identity Manager

book

Article ID: 433759

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

In a high availability deployment of the Java Connector Server (JCS), the Windows service appears to start successfully, but the expected connector listener port (20411) is not opened.

The Connector Server therefore cannot accept provisioning connections from Identity Manager.

JCS service appears running

SERVICE_NAME: im_jcs
DISPLAY_NAME: Symantec Identity Manager - Connector Server (Java)
STATE: RUNNING

JCS process running

tasklist | findstr jcs

jcs.exe PID XXXX

Connector port not listening

netstat -ano | findstr 20411

Result:

(no output)

PowerShell connectivity test fails

Test-NetConnection localhost -Port 20411

Result:

TcpTestSucceeded : False

Environment

Release : 14.5
Component : Identity Manager

Cause

The issue is caused by corrupted or inconsistent JCS runtime cache and internal data files.

Resolution

Clear the JCS cache and runtime data directories so they can be rebuilt during startup.

Steps

Stop the JCS service

Navigate to the Connector Server installation directory.

Example:

<ConnectorServer>\data

Backup and remove the following directories if present:

data\activemq
data\cache
data\derby
data\port
jcs\data\jdbm\etasa
jcs\data\jdbm\SA Configuration

Restart the JCS service

Verify the connector port is now listening

netstat -ano | findstr 20411

Expected result:

TCP 0.0.0.0:20411 LISTENING