DAP Failing to Connect to ASPs over High Latency Networks

(Doc ID 1969135.1)

Last updated on MARCH 30, 2015

Applies to:

Oracle Communications Network Charging and Control - Version 4.0.0 to 5.0.2 [Release 4.0.0 to 5.0]
Oracle Solaris on SPARC (64-bit)


On all versions of Oracle Network Charging and Control (NCC), Data Access Pack (DAP) is used to send SOAP/XML (other protocols are available, please refer to the DAP User and Technical Guide) to Third Party Application Service Providers (ASPs).

Before DAP can exchange application level data (SOAP) with an ASP, it requires the underlying TCP/IP socket connection to be established.

The period which DAP waits for the TCP/IP connection to be established is hardcoded in all versions of NCC/DAP to 1 second before the following ERROR is logged:

ERROR: cannot establish TCP/IP connection to ASP connect() failed with 145: Connection timed out

 This results in a buildup of pending requests in the file configured as "DAP.pendingFilename" in the eserv.config configuration file.


Addition of a DAP Operation which is sent to an ASP over a high latency TCP/IP network.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms