Dear PI Experts,
Recently, our PI system is upgraded from 7.31 to 7.4. In PI 7.31, alert generation was fine. After upgrade, we are facing diffrent issues:
1. Although in Java properties max retry is set to 3 (default), we can see that after reactivation of the alert rules in ID, alerts are getting generated for all the old messages which are in "System error" status, right since 2013. If we check in "Message log" , we can see that number of retry is more than 2000 for all the failed messages.
But as far as I know, if the max retry is set to 3 then PI will change the status to "System Error" after 3 retry.
2. In PI 7.31, Only one alert message got generated for one failed message. But I can see now that in message log if n number of rows which are saiyng about any type of error, are written over there then n number of alert messages got generated although message ID is same for all the alert messages. Mainly, we found this behaviour in Quality system. But in PROD, it is just like previous system i.e. only one alert message got generated for one failed message.
3. Although "missingLastField" & "addidtionalLastField" are set to "ignore" in FCC, we are getting the alert message which syas that 'Detail':java.lang.Exception:Consistency error: field(s) missing - specify 'lastFieldsOptional' parameter to allow this",
Along with the above alert message we are getting one more alert message for same message ID which says that "Unable to archive faulty input file, Inbound/abc.txt to ArchiveFaulty/abc.txt. CAUSE: renameTo failed".
We are getting the above two alert messages altogether.
4. In PROD System, if any message is in "System Error" Status, only one alert message got generated for that error message. If we don't cancel the alert message, no more alert got generated for the same message. But in Quality, if we don't cancel the error message, alert message got generated for the same error message until we cancel that error message.
5. In Quality system, I found one more strange behaviour. After upgrade, alert generation was not working although messages were in "System error" status. Then we created one new alert rule for one new interface. We created the task of "AlertConsumerJob" for the same new interface as well. But I found that, alert got generated using the name of the new alert rule but in message body it is saying about one different interface and one message was in "System error" Status that time for this "different interface".
Could you please explain me what could be the reasons and what all configurations I need to check?
Thanks in advance.
Regards,
Moumita