Greetings. We always get the below INFO message written in the logs.
2016-05-26 11:14:32,179 [ttp-bio-8080-exec-12] [TABTHREAD0] [ ] [ PegaNBAM:07.11] (pplicationPropositionCacheImpl) INFO XXX.XXX.XXX.X|XXX.XXX.XXX.X NBAADeveloper - Proposition cache for top level class NBAM-SR invalidated. It will be refreshed on next access
2016-05-26 11:14:32,180 [ttp-bio-8080-exec-12] [TABTHREAD0] [ ] [ PegaNBAM:07.11] (pplicationPropositionCacheImpl) INFO XXX.XXX.XXX.X|XXX.XXX.XXX.X NBAADeveloper - Refresh proposition cache for top level class NBAM-SR
Sometimes there are many entries in the logs and whilst this is happening in the logs, on the UI i see the busy Inidcator spinning (sometimes it spins for 1220 seconds) and we get requestor lock exceptions.
I also see STUCK threads on System Pulse .
Any ideas why this is happening?
***Updated by moderator: Marissa to remove proprietary information***
Proposition Cache When PRPC is running on multiple system nodes connected to the same database, DSM uses the system pulse to ensure the consistency of propositions across all nodes. The proposition cache is invalidated when a proposition is saved (triggered by adding a proposition, or changing it), or deleted. Adding records that result in the proposition cache to become invalid is done through two declare trigger rules (pyPropositionSaved, and pyPropositionRemoved in the Data-pxStrategyResult class) that run the pyRefreshPropositions activity. Consistent handling of the proposition cache in a multinode PRPC environment requires extra configuration. The configuration is typically performed in the process of installing and configuring PRPC, and described in the topics contained in the Configuration section of the DSM Installation Guide.