My Oracle Support Banner

beServiceTrigger Coredump (Doc ID 2070402.1)

Last updated on FEBRUARY 28, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 4.3.0 to 5.0.3 [Release 4.3 to 5.0]
Information in this document applies to any platform.

Symptoms

On versions of Oracle Communications Network Charging and Control (NCC) 5.0.3 and earlier, the beServiceTrigger process can crash repeatedly due to a SIGABRT (ABORT) while building a Simple Object Access Protocol/Extensible Markup Language (SOAP/XML) request.

There was no special even just before it and the number of pending events from BE_EVENT_STORAGE table was not a factor.

By running mdb on the core file, it can be seen that the process crashes on building the request to OSD:

Changes

 

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
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.