Question
Accenture
IN
Last activity: 12 Dec 2015 9:01 EST
Expired locks are not getting deleted from the Pega 7.1.7 prpc application
Locks are expired in 2 hrs by default.
But their entries are present in the db for 3 day.
Is there something that need to be configured so that whenever a lock is expired it should get deleted from the db?
Actually this is 6.2 prpc application that got upgraded recently to pega 7.1.7.
In 6.2 expired locks gets deleted instantly.
Must be something that need to be configured.
Pegasystems Inc.
US
Rasaiya,
Hello. Are you getting messages that the lock is still held when a requestor tries to open the item or are you just concerned that your database is cluttered? I know that the way we do locking was changed, under the covers, in some fairly significant ways in 6.3, so it's possible they changed when the entry was removed from the database. After a quick search, I wasn't able to find other customers reporting issues being caused by locks not getting removed from the database, so it doesn't look like this is an outstanding problem.
Thanks,
Mike
Hi Mike,
There is an issue reported by the customer for the same issue.
They have upgraded form 6.x to 7.1.7 and now complain that the soft locks that got expired are not deleted from DB.
So this can be considered as an outstanding issue.
Is this the result of change in locking mechanism? If so, what made this change?
Please Advice.
Thank You
Accenture
IN
Hi Mike,
Initially I had locking issue, where the lock created by same user in different session was not able to release.
I read an article regarding locking in pdn forum and created a data instance after which the locking issue got solved.
Now the problem is that the expired locks are not deleted from the database.
I m sure there must b some configuration which is responsible to delete expired lock.
Currently we have created an agent that clears off the expired locks, but there must be some configuration in pega itself.
So was looking for such configuration so that I can delete my agent.
Let me know if you find anything.
Thanks in Advance âºâº
Pegasystems Inc.
US
Pushpaharitha/Rasaiya,
Unfortunately, I don't have much more insight beyond what I already said. Historically the lock info was kept in the table pr_sys_locks. As of PRPC 6.3sp1, some of that was moved to memory. I believe the table is still used so that all the nodes in a multi-node environment are aware of what is locked. I'm pretty sure the system cleaner agent (Defined in Pega-RULES) is supposed to clean these up if it is running, so I'd start by looking at that. If that agent is down, you probably have a lot of other things piling up. You may want to delay and trace it to try and understand why it isn't choosing the remove the locks from the DB. What is the timestamp for the cleanup? I suppose it's possible that you're running into an issue where that stamp is out of sync and they are getting "correctly" cleaned up, but at the time on the stamp and not when you expect.
Thanks,
Mike