How to Set a Sensible DAP "persistentConnectionCheckTimeout" Value When its "persistentConnections" is Enabled
Last updated on SEPTEMBER 16, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.4.0 and later
Information in this document applies to any platform.
NCC's (Network Charging and Control) DAP (Data Access Pack) component can be configured to maintain persistent TCP socket connections to its remote ASPs (Application Service Provider) by enabling its "persistentConnections" parameter. ASP may have idle connection timeouts though and quietly close their connections to DAP. When DAP next sends a message it finds the connection is closed, but instead of reconnecting and resending the message, DAP silently drops the message, which is forever lost. DAP has the "persistentConnectionCheckTimeout" parameter, that needs to be used in tandem with "persistentConnections", to help prevent this type of incident from happening. However, by default the "persistentConnectionCheckTimeout" parameter is set to 0 (disabled), thereby causing unusual and inconsistent DAP behavior such as lost notification messages.
The goal of this article is to further clarify the necessary DAP configuration of these parameters.
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