The Voucher Wallet Server (VWS) "beVWARS" Process Log File is Generating "ccsVWARSReservationExpiry plugin must NOT be run on the Secondary BE" Error Messages on Startup (Doc ID 1193064.1)

Last updated on OCTOBER 18, 2016

Applies to:

Oracle Communications Network Charging and Control - Version: 2.4.0 and later   [Release: 2.4 and later ]
Information in this document applies to any platform.

Symptoms

If the ccsVWARSReservationExpiry plugin is configured to run on the secondary Voucher Wallet Server (VWS - legacy term Universal Billing Engine (UBE)) then the following error message will appear in the beVWARS process(es) log file, for each beVWARS process that has been configured to run.
Aug 24 12:27:05.913365 beVWARS(7987) ERROR: The ccsVWARSReservationExpiry plugin must NOT be run on the Secondary BE. Stop the BE and remove it from the list of plugins in eserv.config
The ccsVWARSReservationExpiry is designed to only run on the primary VWS in a logical pair.

On: BE 2.4.0.22 version of Voucher Wallet Server.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. On the secondary VWS, in the BE.beVWARS.plugins section of the /IN/service_packages/eserv.config file, add an entry for the ccsVWARSReservationExpiry.so library file.

/IN/service_packages/eserv.config:

BE = {
...skipped..

     beVWARS = {
     ...skipped...

         # ccs plugins to be loaded by the beVWARS
        plugins = [
        ...skipped...
            "ccsVWARSReservationExpiry.so"
        ]


2. Restart the SLEE on the secondary VWS.

3. On startup of the beVWARS process(es) will report the error message.

BUSINESS IMPACT
---------------------------
The issue has the following business impact:

Configuring the BE.beVWARS.ccsVWARSReservationExpiry plugin activates the Used Unit Confirmation (UUC) feature. This plugin will fire when wallet reservations for charging transactions have not responded in the configured time period so the beVWARS process(es) expires the transaction.  For example, during a call session, the VWS does not receive the next Subsequent Reservation (SR), or Commit Reservation (CR) request from the beClient, as expected.  This may occur due to lost network traffic (e.g. AWOL calls: no applyCharging (AC), or applyChargingReports (ACR) received), or software failure (USP SLEE process failure e.g. slee_acs, beClient).

When the UCC feature is not activated, if reservation expiration occurs, then the billing units, used in the call (or charging session) so far, will be revoked and hence no value is deducted from the subscriber's account for the entire call.

When the UCC feature is activated, if reservation expiration occurs, then the VWS will commit the used billing units confirmed so far (all the SR received before reservation timeout) and deduct value from the subscriber's account.

This line should only be added on the Primary VWS because in normal operation, a wallet reservation will expire at exactly the same time on both VWS's.  Configuring the ccsVWARSReservationExpiry plugin on the Secondary VWS will cause the subscriber to be double-charged.

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