Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

Attendant Console 1.1 fails to start with the "RMI Server: java.rmi.server.ExportException: Port already in use: 1099" error message

Core Issue

When the Cisco CallManager Attendant Console server and the Apps/eServices/Customer Response Applications (CRA)/Customer Response Solution (CRS) package are installed on the same server, the Interactive Call Distribution (ICD) component of Apps may stop functioning. MIVR logs may show this error message.

When both the Attendant Console server and Apps/eServices/CRA/CRS are installed on the same Cisco CallManager server, The Cisco Telephony Call Dispatcher (TCD) service for the Attendant Console starts and binds a Remote Method Invocation (RMI) server to port 1099. Then the Cisco Application Engine starts and attempts to bind to port 1099, but the port is already in use. This is a race condition on service startup. If the Cisco Application Engine starts first, the TCD uses the first available port after 1099.

Resolution

This problem is fixed in Attendant Console release 1.1(2.105) by Cisco bug ID CSCdx47467. The Cisco Application Engine service starts automatically. Then manually  start the TCD service. This way, the race condition is avoided and both CRA and the Attendant Console start.

For a workaround to this problem, set the TCD service startup type to Manual and reboot the server.

Version history
Revision #:
1 of 1
Last update:
‎06-22-2009 03:41 PM
Updated by:
 
Labels (1)