Question
Dell
US
Last activity: 28 Sep 2017 17:19 EDT
Latest rules are not getting executed.
Pega 7.1.7, after we import rules into testing and production environments, latest rules are not getting reflected and still old rules are getting executed. And sometimes its happening for only particular access group. In any situation, if we Revalidate and Save, it will work fine. But its very cumbersome to find which rule not getting executed correctly and do this step.
Thinking there should be a hot fix or configurations missed. Can any one provide insights, please?
***Moderator Edit: Vidyaranjan | Updated SR details***
Pegasystems Inc.
US
What database are you using? HFix-23344 addresses an issue where not all of the cache shortcuts were invalidated. This hot fix applies to SQL Server.
How many nodes are in the environment? Does the issue occur on all of the nodes? Or is the proper section displayed on the import node but not the other nodes?
Here are some useful debugging steps. It looks like you already have an SR open. If the issue is reproducible, you could follow these steps to enable logging and collect the cache details. The GCS engineer can review the results.
Troubleshooting Steps
What database are you using? HFix-23344 addresses an issue where not all of the cache shortcuts were invalidated. This hot fix applies to SQL Server.
How many nodes are in the environment? Does the issue occur on all of the nodes? Or is the proper section displayed on the import node but not the other nodes?
Here are some useful debugging steps. It looks like you already have an SR open. If the issue is reproducible, you could follow these steps to enable logging and collect the cache details. The GCS engineer can review the results.
Troubleshooting Steps
- Debug logging can be enabled on these classes prior to the import to output log messages related to the cache invalidation.
- com.pega.pegarules.deploy.internal.util.ImportImpl
- com.pega.pegarules.generation.internal.cache.appcentric.RACacheAppCentricImpl
- com.pega.pegarules.generation.internal.vtable.VirtualTableImpl
- If you find the wrong version of a stream rule is running, use SMA (System Management Application) to collect the cache reports.
- In SMA, go to Advanced -> Application Based Assembly Cache Management
- Put the rule name in the RULE NAME text box.
- While viewing the list of assembled class names for that rule name, you could use the radio buttons and the Remove from Cache button. This removes that one class from the memory cache. It does not affect the database.
- You could try this and see if it alleviates the problem. If so, please let us know about this as it is evidence of memory state problems likely due to pulse processing.
- In the upper Right, find the Database reports. And press Database – Dependencies
- That will produce a csv file
- Download it and save it with a name that includes “Deps” in the file name
- And press Database – Shortcuts
- That will produce a csv file
- Download it and save it with a name that includes “Shortcuts” in the file name
- And press Database – Entries
- That will produce a csv file
- Download it and save it with a name that includes “Entries” in the file name
- Collect the generated java for the rule.
- In SMA, go to Advanced -> Application Based Assembly Cache Management
PEG
US
See SA-18971. You probably want to add or modify the prconfig setting "systempulse/scanoffsetms", and set it to 30000.
The full syntax for the setting is
<env name="systempulse/scanoffsetms" value="30000"/>
You will need to restart the JVM after making the change.