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 and later   [Release: 4.0.0 and later ]
Information in this document applies to any platform.


This document explains how to read and understand the following message, commonly seen on production systems:

# 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


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