dapIF Ignores Server Initiated Socket Closures and Silently Loses a Request
(Doc ID 2942047.1)
Last updated on JULY 19, 2024
Applies to:
Oracle Communications Network Charging and Control - Version 4.3.0 to 12.0.6.0.0 [Release 4.3 to 12.0.0]Oracle Communications Convergent Charging Controller - Version 6.0.0 to 12.0.6.0.0 [Release 6.0 to 12.0.0]
Information in this document applies to any platform.
Symptoms
On all version of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C) up to and including 12.0.6.0, there is an issue with Data Access Pack (DAP or dapIF) where it fails to handle a socket closure sent by the server dapIF is connected to.
A socket is deemed closed when a Transmissions Control Protocol (TCP) packet with the FIN control flag set, is sent/received between 2 endpoints.
In this scenario of the server side sending the TCP FIN, dapIF only processes this socket closure when a new DAP request is triggered from an Advanced Control Services (ACS) Control Plan (CP). This request is also silently lost.
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 |
Cause |
Solution |
References |