A workaround is to increase this parameter to accommodate messages with more than 1000 components.
On the Enforce server, in /Vontu/Protect/config modify the IncidentPersister.properties and increase the following parameter:
# max.component.per.message is the maximum number of message components in an incident
max.component.per.message=1000
Increase this to a higher number that will let the incident persister process incidents.
However, this change can result in Out of Memory (Java) and process time out issues.
If there are OOM or time out issues, the Java Heap space for the Vontu Incident Persister may need to be doubled.
Check the JVM memory properties in /Vontu/Protect/config/VontuIncidentPersister.conf.
Double the following parameters:
# Initial Java Heap Size (in MB)
wrapper.java.initmemory=XXXX
# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=YYYY
Where XXXX and YYYY are double the previous values.