Read and Understand the beVWARS "Timed out x wallet reservation" Messages
(Doc ID 1399435.1)
Last updated on SEPTEMBER 12, 2016
Applies to:Oracle Communications Network Charging and Control - Version: 4.0.0
Information in this document applies to any platform.
# grep "ERROR: Timed out" /IN/service_packages/E2BE/tmp/beVWARS.log
beVWARS(7199) ERROR: Timed out 1 wallet reservation:[clientId 9142449, clientMsgId 12141985], current time 20111125160446, expired 20111124233310 (59496 seconds ago), message timestamp 20111124113310.759822, not from beServer
This document does not
- explain how the beVWARS defines the validity of a Reservation.
- explain how and when the beVWARS decides to remove Dead Reservation from its cache. Please read the following article : "beVWARS Voucher and Wallet Cache Management (Doc ID 1399453.1)"
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
Introduction : The beVWARS reservation cache and reservation time outs
A closer look to that message
What does "clientID" mean ?
What does "clientMsgId" mean ?
What does "current time" mean ?
What does "expired" and "seconds ago" mean ?
What does "message timestamp" mean ?
A picture is worth a thousand words...