diameterControlAgent Crashes if GGSN Continues Sends Requests for Invalid MSCC Session
Last updated on DECEMBER 11, 2015
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.
In all versions of Oracle Communications Network Charging and Control (NCC), a problem exists in the diameterControlAgent process where it can crash (due to a Segmentation Fault (SEGV)) if a Gateway General Packet Radio Service (GPRS) Support Node (GGSN) continuously tries to request more units from a MSCC sub-service which the diameterControlAgent has already released.
The following error may be seen in the diameterControlAgent.log just before it crashes:
Possible integration with new GGSN or some new type of DIAMETER traffic is hitting the diameterControlAgent.
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