Each BeVWARS Process Spawned BeVWARS Results In 32 Processes (instead Of 16)
(Doc ID 2513406.1)
Last updated on OCTOBER 16, 2019
Applies to:Oracle Communications Network Charging and Control - Version 5.0.1 and later
Information in this document applies to any platform.
Each beVWARS process spawned beVWARS results in 32 processes (instead of 16).
During the planned Voucher and Wallet Server (VWS) fail over testing, the SLEE was restarted on Secondary VWS after beVWARS was aborted.
SLEE has restarted but got 32 beVWARS processes (instead of 16 as per SLEE.cfg). The 32 processes all match up to one child process per parent beVWARS process.
Why are there 32 beVWARS processes and what is their purpose?
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