BeServiceTrigger Coredumps after receiving a SIGSEGV or a SIGBUS (Doc ID 2093710.1)

Last updated on NOVEMBER 07, 2016

Applies to:

Oracle Communications Network Charging and Control - Version 5.0.2 and later
Information in this document applies to any platform.

Symptoms

The role of beServiceTrigger:
beServiceTrigger sends Business Process Logic (BPL) requests to instances of the xmlTcapIF and Network Charging and Control (NCC) Open Services Development (OSD) requests to the osdInterface running on separate Service Logic Controller (SLC) nodes within the same Intelligent Platform(IN) platform. It runs as a SLEE interface on the primary VWS only.
beServiceTrigger accepts beServiceTrigger events from other Billing Engine (BE) SLEE interfaces running on the same Voucher and Wallet System (VWS).

The problem is that the beServiceTrigger process is generating core files.

It is expected that the beServiceTrigger should work without generating core files.

Changes

 

Cause

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