The following messages are seen in the TSIM eventws log while creating events through the Rest API: ERROR 06/24 10:56:05 [Thread-90,EXECUTOR_POOL::ss004626:1591486034159::] AbstractEventConverter Method: doSlotMapping, error: Map Not found, error: FUNC:NGPEvent::map::::Either mapOfMap or mapOfMap.get(mapName) is null WARN 06/24 10:56:05 [Thread-90,EXECUTOR_POOL::ss004626:1591486034159::] DefaultEventConverter Method: doSlotMapping, event after mapping is null, hence using event with out slot mapping |
The messages are mis-categorized as an ERROR and are seen while creating events through the REST API. The API tries to verify if this generated event needs some special handling in regard to slots. In order to do so, it searches for the MapName in MapFile.map (has some predefined slot mappings) which exists under <installationdirectory>\pw\pronto\conf directory. This file is currently being referred to by some internal events which need some special handling for the incoming slot values. It is also being referred to through the REST APIs as well to check if the incoming event needs that special handling of the slots. If the map name is not found in that file, the error message is thrown indicating the map was not found and will continue with the provided slots. The error messages seen in the eventws.log should be INFO messages, not an ERROR message, because these messages are harmless and just informing that no special mapping of slots has been found. Product defect DRTRF-79 is open to address this in a future release. |