Saved Data File; Timed Out Waiting For Callback; Timeout Refreshing Map - Novell SENTINEL RAPID DEPLOYMENT 6.1 - 12-2009 User Manual

B.5.13 Saved Data File
Table B-60
Tag
Severity
Event Name
Resource
SubResource
Message
B.5.14 Timed Out Waiting For Callback
When the Collector Manager needs to refresh a map, it sends a request to the back end. This request
contains a callback. The back-end generates the map and when it is ready it sends the map to the
Collector Manager, using the callback. If it takes too long for the response to arrive (more than ten
minutes) the Collector Manager submits a second request assuming the first was lost. When this
occurs, the following internal event is generated:
Table B-61
Tag
Severity
Event Name
Resource
SubResource
Message
B.5.15 Timeout Refreshing Map
This internal event is generated from the client side of the mapping service (the one that is part of the
Collector Manager). When the Collector Manager is told to refresh the map because it has been
modified or its definition has changed it sends an internal. This means that the Collector Manager
attempted to retrieve the map from the server and the server never acknowledged the request and
timed out. This error is considered transient and the Collector Manager retries.
Table B-62
Tag
Severity
436 Sentinel 6.1 Rapid Deployment User Guide
Database Aggregation : Saved Data File
Value
SavedDataFile
MappingService
MapService
Saved "+fileSize+" bytes to file <fileName> with original backed up to
"+backupFile:"no backup of original
Database Aggregation : Timed Out Waiting For Callback
Value
2
TimedoutWaitingForCallback
MappingService
ReferentialDataObjectMap
Map <name> timed out waiting for callback with new map data--retrying
Database Aggregation : Timeout Refreshing Map
Value
4