The evaluation of the pm-mapper has shown that an xml file is sometimes processed twice during operation.
In the attached attachment you can see this evaluation of the logs, data-router database and code analysis (BUG1 and especially BUG2) [BUG3 and 4 have already been reported].
The double processing of xml files has its origin in a weakness of the implementation. The code is not designed for concurrency. The problem is that the data router provides an xml file, this is processed (but takes too long) and the data router makes a retry within a time (5s) and this is then processed again. This of course results in a duplication of the VES messages and thus counters in the system.
We tried the workaround, but it does not provide 100% security. This reduces the number of messages processed twice, but has not disappeared.
The following points would have to be adjusted in the implementation:

• The processing must be synchronized so that it is impossible for xml files sent twice to be processed more than once
• The implementation has to be adjusted so that the pm-mapper can be scaled across multiple instances. This is currently not possible because the status is kept in memory. Our load test showed that the pm-mapper is the bottleneck in the chain.
• Implementation of retry mechanism to report successful processing to the data router.