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.
Tag |
Value |
Severity |
2 |
Event Name |
TimedoutWaitingForCallback |
Resource |
MappingService |
SubResource |
ReferentialDataObjectMap |
Message |
Map <name> timed out waiting for callback with new map data--retrying |
ErrorApplyingIncrementalUpdate
This event is sent when the mapping service fails to apply an update to an existing client map.
Tag |
Value |
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. |
OutOfSyncDetected
This event is sent when the mapping service detects that a map is out of date. The mapping service will automatically schedule a refresh.
Tag |
Value |
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 |