My Oracle Support Banner

The OCA GUI could not connect to the OCA server. (Doc ID 441849.1)

Last updated on OCTOBER 12, 2016

Applies to:

Oracle Communications ASAP - Version 4.5.0 to 5.2.4 [Release 4.5 to 5.2]
Oracle Solaris on SPARC (32-bit)
***Checked for relevance on 28-Aug-2012***


Symptoms

Description

OCA was looping and the CPU usage by OCA server was at 99%. The OCA process would not terminate normally and had to be manually killed. When the problem happened there was no database issue in accessing the SARM database to retrieve data from the tables. The CORB diag always showed this message right before the problem occurrence

>> 091905.495:PROG:System Event :191 :Listener.cpp.Thread:SRP_Listener_eventASAP System Event: SYS_TERM Cannot bind socket to port: Address already in use.

Impact

OCA users lose access to the application until the OCA server is manually restarted by the client [ stops/starts OCA ]

Error Message

The CORB diag always showed this message right before the problem occurrence

>> 091905.495:PROG:System Event:191 :Listener.cpp.Thread:SRP_Listener_eventASAP System Event: SYS_TERM Cannot bind socket to port: Address already in use.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
 Description
 Impact
 Error Message
Cause
Solution
 Resolution
 WorkAround

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.