DAP Late at Clearing Timed Out Requests
Last updated on MAY 08, 2017
Applies to:Oracle Communications Network Charging and Control - Version 4.0.0 and later
Oracle Solaris on SPARC (64-bit)
In all current versions of NCC (Network Charging and Control), an issues exists in DAP (Data Access Pack) where timed out DAP requests to an ASP (Application Service Provider) are not correctly processed on time. This means it is not possible to correctly configure cascading timeouts due to the unpredictability of when dapIF (DAP Interface) will respond.
When creating DAP request templates, the timeout configured in the screens is the duration (in milliseconds) that dapIF should wait for a response:
However, under low traffic or test conditions, then it can be up to the WATCHDOGCYCLETIME + DAP Request Configured Timeout before the timed out request is actually cleaned up by both dapIF and slee_acs.
Problems with the ASP which may be causing it not to respond to dapIF in a timely manner.
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