DAP Real Time Wallet Notifications Fail with Exception "Notification value name too long, value = <NOTIFICATION_NAME> maximum size = 41" (Doc ID 2045680.1)

Last updated on MAY 05, 2017

Applies to:

Oracle Communications Network Charging and Control - Version 4.3.0 and later
Oracle Solaris on SPARC (64-bit)

Symptoms

In all versions of Oracle Communications Network Charging and Control (NCC), Real Time Wallet Notifications (RTWNs) are used to notify subscribers of specific events such as expiry, recharges etc. which have taken place against their wallet.

NCC offers the ability to configure these RTWNs as either Short Message Service (SMS) templates or Data Access Pack (DAP) templates depending on how the solution is expected to fit into a network.  More information on this is available in the Charging Control Services (CCS) User Guide.

When using DAP templates, a problem exists where the RTWN can fail at runtime (ie. when it is triggered), due to the length of the configure RTWN name:

Jul 10 20:23:44.917948 beVWARS(15190) WARNING: Processing Exception on VWARS while processing be::Protocol Message: be VWARS RuntimeError: Error running plug-in 'ccsNotification.so:activeBalanceValueChangedEvent': be VWARS RuntimeError: Plug-in error: Notification value name too long, value = NOTIFICATION_NAME maximum size = 41

Changes

Creation of a new RTWN with an exceptionally long name.

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