beServiceTrigger Coredump (Doc ID 2070402.1)

Last updated on NOVEMBER 02, 2016

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.


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:

# mdb core-20700-beServiceTrigger
Loading modules: [ ]
> ::showrev
Hostname: vws11
Release: 5.11
Kernel architecture: sun4v
Application architecture: sparc
Kernel version: SunOS 5.11 sun4v 11.1
Platform: sun4v
> ::status
debugging core file of beServiceTrigge (32-bit) from vws11
file: /IN/service_packages/E2BE/bin/beServiceTrigger_21652583_2
initial argv: /IN/service_packages/E2BE/bin/beServiceTrigger
threading model: native threads
status: process terminated by SIGABRT (Abort), pid=20700 uid=1002 code=-1
> $G
C++ symbol demangling enabled
> ::stack`_lwp_kill+8(6, ffffffef, ffffffec, ffbfecb0, 5, 6)`abort+0x108(fd8885e0, fd6de1ec, 6, 1, fd6dfa80, 0)`__cxxabiv1::__terminate+4(9b930, fd8b450c, b48c0, 0, bee946e8, ffbfeab0)`std::terminate+0x1c(0, 1, bee946b8, 9b930, 0, bee94700)`__cxa_throw+0x8c(bee946e8, fd8b4530, fd888860, 89c, 1, fd6e51ac)`operator new+0x9c(3f6eff0, fd8b4184, 280, 0, 140, fd6e51ac)`std::__default_alloc_template<true, 0>::_S_chunk_alloc+0xac(b7b538e8, ffbfefec, 0, 2944, fa962a40, 14)`std::__default_alloc_template<true, 0>::_S_refill+0x1c(10, 0, 0, 0, 9cc00, 0)`std::__default_alloc_template<true, 0>::allocate+0xec(0, 4, 9c910, 15, b7b52544, 9e8)`std::basic_string < char, std::char_traits<char>, std::allocator<char> >::_Rep::_S_create+0x6c(1, 0, 0, 35, f7f731f4, 4)`char* std::basic_string < char, std::char_traits<char>, std::allocator<char> >::_S_construct<const char*>+0x2c(c453320b, 1, ffbff290, ffbff1cf, ff0000, 80808080)`std::basic_string < char, std::char_traits<char>, std::allocator<char> >::basic_string +0x28(ffbff288, c453320b, ffbff290, 16, 1, 0)
void be::ServiceTrigger::getRequestData<be::ServiceTrigger::Dap2RequestEvent_v2>+0x110(c453320b, 1, beeaae40, beeaae44, beeaae50, ffbff250)
be::ServiceTrigger::Request::Request+0x19c(9bc00, c4532b50, beeaae5c, beeaae60, 1, fd6e51ac)
be::ServiceTrigger::OsdRequest::OsdRequest+0x10(beeaae18, c4532b50, 9cf98, fd8b2520, 378fc, 0)
be::ServiceTrigger::OsdRequestBuilder::buildRequestconst+0x2c(b4860, c4532b50, 9bce8, 32120, b4860, fd6e51ac)
be::ServiceTrigger::OperationDefinition::constructRequest+0x18(ffbff4e8, c4532b50, ffbff470, a2f00, ffbff458, 9e8)
be::ServiceTrigger::RequestFactory::createRequest+0xc0(a2ef8, c4532b50, ffbff510, 9e8, 9e8, 9e8)
be::ServiceTrigger::Interface::processServiceTriggerEvent+0x1c(a36b8, c4532b50, 520, 9c0, 524, 5a8)
be::ServiceTrigger::Interface::run+0x36c(a36b8, 0, c0602330, 0, 9cbcc, fd6de1ec)
main+0x184(0, ffbff714, ffbff71c, 9cbcc, 0, fa960180)
_start+0x5c(0, 0, 0, 0, 0, 0)

beServiceTrigger - beServiceTrigger sends SOAP/XML requests to instances of the xmlTcapIF and osdInterface. It runs as a SLEE interface on both the Voucher Wallet Servers (VWS')
BE_EVENT_STORAGE - a database table used to store events on the VWS that are to be retried later
mdb - a Solaris tool that provides helpful information about the process stack at the time of the crash. Usage:

$ mdb <core_file>


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