Expired Reservations Remains on VWS Even After the Configured Value of 'Hold Time' Has Been Reached
Last updated on OCTOBER 18, 2016
Applies to:Oracle Communications Network Charging and Control - Version 4.4.1 and later
Information in this document applies to any platform.
Currency check on 23-03-2015
While testing for mid-session commit on Network Charging and Control (NCC) version 4.4.1, it's found that the Voucher and Wallet Server (VWS) does not expire reservations after the configured value of 'Hold Time' has been reached. The reservation remains on the VWS forever.
In beVWARS debug log, the last SR (Subsequent Request) coming at "2013/02/10 12:24:06":
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