My Oracle Support Banner

beServer Crashes on the VWS after a beVWARS Crash (Doc ID 2978524.1)

Last updated on OCTOBER 05, 2023

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]
Information in this document applies to any platform.

Symptoms

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC), when running multiple beServer instances on the Voucher Wallet Server (VWS), beServer can crash shortly after a beVWARS crash.

The beServer that crashes is always the first instance (beServer0) and cannot be avoided unless the configuration is reverted back to a single beServer instance, or preventing any causes of the beVWARS crash.

The stack trace shows beServer is crashing due to a Segmentation Fault (SIGSEV) when processing data it is reading from a socket:

Program terminated with signal SIGSEGV, Segmentation fault.
...
#10 <signal handler called>
#11 0x000000010005c568 in cmn::dpSocketAdaptor<be::Protocol::Message>::dataAvailable (this=0x102666bd0, fd=...)
    at /<PATH>/cmndpSocketAdaptor.hh:451
#12 0xffffffff64d0855c in cmn::dpFD::readData (this=0x10078cdb0) at cmndpFD.cc:302
#13 0xffffffff64d09190 in cmn::dpFDManager::processFdSet (this=this@entry=0x10078d9c8, first=first@entry=0x10078da00, last=<optimized out>) at cmndpFD.cc:593
#14 0xffffffff64d098c8 in cmn::dpFDManager::poll (this=this@entry=0x10078d9c8, timeout=timeout@entry=0xffffffff7fffe7e0) at cmndpFD.cc:759
#15 0x0000000100054fc4 in be::IF::ClientManager::poll (this=0x10078d960, timeout=0xffffffff7fffe7e0) at beServerIFClient.cc:283
#16 0x0000000100039184 in be::IF::ServerIF::pollClients (this=this@entry=0x1001c8140, timeout=timeout@entry=0xffffffff7fffe7e0) at beServerIF.cc:569
#17 0x000000010004d300 in be::IF::ServerIF::doRunningState (this=this@entry=0x1001c8140) at beServerIF.cc:290
#18 0x000000010004d984 in be::IF::ServerIF::run (this=0x1001c8140) at beServerIF.cc:105
#19 0x0000000100027388 in main (argc=<optimized out>, argv=0xffffffff7fffea38) at beServer.cc:62

This issue can be reproduced by killing any beVWARS process when multiple beServer instances are running.

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


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