Preventing Orphaned VWS Responses by Cascading Timeouts
Last updated on JANUARY 04, 2017
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (NCC), an orphaned response is any response which arrives after the recipient has already timed out the context which relates to the late response. Due to poorly configured timers, this can occur between the BeClients running on the Service Logic Controllers (SLCs) and the Voucher Wallet Servers (VWS').
When an orphaned message is received, the BeClient logs the following alarm to its log file:
Nov 25 14:26:55 SLC01 BeClient: [ID 675952 user.error] BeClient(29994) ERROR: In last 10 seconds we received 1 orphaned response from primary BE 1.
The aforementioned alarms will usually be preceded by the following timeout alarm:
Slower VWS responses and/or the timers were reconfigured without consulting Oracle Support.
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