Support Article
Rule Resolution Issue After Code Deployment
SA-79924
Summary
After deploying a new code in Production, duplicate rules display. The duplicates have nearly-identical pzInsKeys with only the timestamps differing by a few milliseconds
For example,
RULE-OBJ-PROPERTY ABCD-FW-ARFW-DATA-PPRTHRESHOLD SUBORGNAME #20190222T084427.178 GMT
RULE-OBJ-PROPERTY ABCD-FW-ARFW-DATA-PPRTHRESHOLD SUBORGNAME #20190222T084427.181 GMT
Error Messages
PEGA Logger com.pega.pegarules.exec.external.basic.conclusions.AbstractClassResolvableConclusion throws a Warning message in the logs that rule resolution can't find the rule.
[ttp-nio-8443-exec-20] [TABTHREAD2] [ ] [FinoColWB:01.02.01] (tractClassResolvableConclusion) WARN a.b.com|127.0.0.1 JJones - Rule Resolution should have returned a single rule, but 2 rules were returned
Steps to Reproduce
Send mail through a local flow action.
Root Cause
A defect in Pegasystems’ code or rules.
Two users or agents can work on the same item within a few milliseconds and each process will create a new rule.
If the operation is to create a new copy of a rule, then both the copies are created with slightly different timestamps in the pzInsKey.
Resolution
Perform the following local-change to prevent two users or agents from working on the same item at the same time:
Add the below prconfig setting:
<env name="/database/maxlockattempts" value="1"/>
Published August 15, 2019 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.