B.7 Mapping Service
Below listed are relevant to mapping service
B.7.1 Error
Table B-51 Database Aggregation - Error
|
Severity
|
|
|
Event Name
|
error
|
|
Resource
|
|
|
SubResource
|
|
|
Message
|
Error while updating map data: {0}
|
B.7.2 Error Applying Incremental Update
This event is sent when the mapping service fails to apply an update to an existing client map.
Table B-52 Database Aggregation - Error Applying Incremental Update
|
Severity
|
4
|
|
Event Name
|
ErrorApplyingIncrementalUpdate
|
|
Resource
|
MappingService
|
|
SubResource
|
ReferentialDataObjectMap
|
|
Message
|
The error <error> occurred while applying updates to map <mapName> (ID <mapId>) v.<version>. Rescheduling a refresh to complete map update. |
B.7.3 Error initializing map with ID
This internal event is generated from the client side of the mapping service (the one that is part of the Collector Manager). This error is generated when the Collector Manager attempts to retrieve a map that does not exist. This should not happen but can happen if maps are created and deleted.
Table B-53 Database Aggregation - Error initializing map with ID
|
Severity
|
4
|
|
Event Name
|
ErrorNoSuchMap
|
|
Resource
|
MappingService
|
|
SubResource
|
ReferentialDataObjectMap
|
|
Message
|
Error initializing map with id <ID>: no such map
|
B.7.4 Error 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 event. This means that there was some unexpected non-transient error while trying to refresh a map. The Collector Manager will wait 15 minutes and will try again. If this happens during initialization the initialization will proceed and this map will be ignored until it can be successfully loaded.
Table B-54 Database Aggregation - Error Refreshing Map
|
Severity
|
4
|
|
Event Name
|
ErrorRefreshingMapData
|
|
Resource
|
MappingService
|
|
SubResource
|
ReferentialDataObjectMap
|
|
Message
|
Error refreshing map <mapName>: <exc> |
B.7.5 Error Saving Data File
Table B-55 Database Aggregation - Error Saving Data File
|
Severity
|
|
|
Event Name
|
ErrorSavingDataFile
|
|
Resource
|
MappingService
|
|
SubResource
|
MapService
|
|
Message
|
The error <error> occurred while saving data to file <fileName> (no) backup
|
B.7.6 Get File Size
Table B-56 Database Aggregation - Get File Size
|
Severity
|
|
|
Event Name
|
getFileSize
|
|
Resource
|
|
|
SubResource
|
|
|
Message
|
Retrieving size for file <fileName>
|
B.7.7 Loaded Large Map
This internal event is an information event sent by the mapping service informing that a large map was loaded to the Collector Manager. A map is considered large if the number of rows exceeds 100,000.
Table B-57 Database Aggregation - Loaded Large Map
|
Severity
|
0
|
|
Event Name
|
LoadedLargeMap
|
|
Resource
|
MappingService
|
|
SubResource
|
ReferentialDataObjectMap
|
|
Message
|
Finished loading map <name> with id <ID> and <number> entries and total size <#>Kb in <##>sec |
B.7.8 Long Time To Load Map
This internal event is an information event sent by the mapping service informing that loading a map took an unusually long time (greater than one minute).
Table B-58 Database Aggregation - Long time To load Map
|
Severity
|
0
|
|
Event Name
|
LongTimeToLoadMap
|
|
Resource
|
MappingService
|
|
SubResource
|
ReferentialDataObjectMap
|
|
Message
|
It took <##>sec to load map <name> with id <ID> and <number> entries and total size <##>Kb |
B.7.9 Out Of Sync Detected
This event is sent when the mapping service detects that a map is out of date. The mapping service will automatically schedule a refresh.
Table B-59 Database Aggregation - Out Of Sync Detected
|
Severity
|
2
|
|
Event Name
|
OutOfsyncDetected
|
|
Resource
|
MappingService
|
|
SubResource
|
ReferentialDataObjectMap
|
|
Message
|
Map <mapName> detected the map data is out-of-sync, probably because of a missed update notification--scheduling a refresh |
B.7.10 Refreshing Map from Cache
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 event. This means that its cache is up to date and is refreshing the map from cache.
Table B-60 Database Aggregation - Refreshing Map from Cache
|
Severity
|
1
|
|
Event Name
|
LoadingMapFromCache
|
|
Resource
|
MappingService
|
|
SubResource
|
ReferentialDataObjectMap
|
|
Message
|
Loading from cache v<version> of map <mapName> (ID <id>) |
B.7.11 Refreshing Map from Server
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 event. This means that the map was either not in the cache or the version in the cache was not up to date and the Collector Manager is retrieving the map from the server.
Table B-61 Database Aggregation - Refreshing Map from Server
|
Severity
|
1
|
|
Event Name
|
RefreshingMapFromServer
|
|
Resource
|
MappingService
|
|
SubResource
|
ReferentialDataObjectMap
|
|
Message
|
Refreshing from server map <name> with id <ID>
|
B.7.12 Save Data File
Table B-62 Database Aggregation - Save Data File
|
Severity
|
|
|
Event Name
|
saveDataFile
|
|
Resource
|
|
|
SubResource
|
MapService
|
|
Message
|
Saving data file {0}, backup? {1}
|
B.7.13 Saved Data File
Table B-63 Database Aggregation - Saved Data File
|
Severity
|
|
|
Event Name
|
SavedDataFile
|
|
Resource
|
MappingService
|
|
SubResource
|
MapService
|
|
Message
|
Saved "+fileSize+" bytes to file <fileName> with original backed up to "+backupFile:"no backup of original
|
B.7.14 Timed Out Waiting For Callback
When the Collector Manager needs to refresh a map it sends a request to the backend. This request contains a callback. The backend 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 will submit a second request assuming the first was lost. When this occurs, the following internal event is generated.
Table B-64 Database Aggregation - Timed Out Waiting For Callback
|
Severity
|
2
|
|
Event Name
|
TimedoutWaitingForCallback
|
|
Resource
|
MappingService
|
|
SubResource
|
ReferentialDataObjectMap
|
|
Message
|
Map <name> timed out waiting for callback with new map data--retrying
|
B.7.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 will retry.
Table B-65 Database Aggregation - Timeout Refreshing Map
|
Severity
|
4
|
|
Event Name
|
TimeoutRefreshingMap
|
|
Resource
|
MappingService
|
|
SubResource
|
ReferentialDataObjectMap
|
|
Message
|
Request timed out while refreshing map <name>: <exception>
|
B.7.16 Update
Table B-66 Database Aggregation - Update
|
Severity
|
|
|
Event Name
|
update
|
|
Resource
|
|
|
SubResource
|
MapDataCallback
|
|
Message
|
Updating map data
|
B.7.17 Update
Table B-67 Database Aggregation - Update
|
Severity
|
|
|
Event Name
|
update
|
|
Resource
|
|
|
SubResource
|
(low)
|
|
Message
|
Updating map data (ser)
|