Question

3
Replies
529
Views
MichaelF1903 Member since 2012 26 posts
CYBG
Posted: 4 years ago
Last activity: 3 years 11 months ago
Closed
Solved

pzDeleteExpiredLocks - 3-day removal of old locks hard-coded?

Hi,

 

I'm attempting to debug some issues with locks not being removed cleanly. I've created the dynamic system setting to avoid the internal lock caching* so I can overcome the problem by manually removing the offending PR_SYS_LOCKS entries ourselves - apologies Pega, we have no other choice.

 

However, upon investigation I came across the pzDeleteExpiredLocks activity, which appears to be hard-coded to only clean expired locks when they are 3 days old. Unfortunately the RDB-Delete rule this activity then calls is hidden so we can't prove that that's what it's doing.

 

Please can someone confirm whether:

a) this is correct,

b) whether future versions of PRPC will have this value changed to a dynamic system setting to allow us to control when expired locks are purged. The three-day limit is not one we're happy with, we'd prefer to limit it to a few hours.

 

If we can't change this then we'll simply implelment our own agent to clean up more frequently, but it would be nice to use the OOTB agent activity.

 

Many thanks,

 

Mike.

 

* prconfig/database/lockcache/enabled/default in Pega-Engine class, set to false

System Administration
Moderation Team has archived post
Share this page LinkedIn