Discussion
Pegasystems Inc.
US
Last activity: 23 Sep 2019 14:09 EDT
Pega Proactive Notice: Thread Locking
- Pega 8.1
- Pega 8.1.1
- Pega 8.1.2
- Pega 8.1.3
- Pega 8.1.4
- Pega 8.1.5
- Pega 8.2
- Pega 8.2.1
- Pega 8.2.2
Ford Motor Company
US
Are there any Proactive Notices Avaible for 7.x Series (especially after 7.3.x) or 7.4.x, thanks!
Pegasystems Inc.
US
There are not, nor are there plans to do so in the future. However, we did recently do a community collaboration to catalog all 7.x critical hot fixes. This provides a single reference for 7.x installs to ensure they are current with the hot fixes Pega has deemed critical for secure and performant deployments.
Ford Motor Company
US
Thank you Brendan. 7.x Link you have provided doesnt have any HFix's mentioned for 7.3.1 or Higher Versions, can I assume,no Critical HFIXs avaiable for those PRPC Versions or the Page not updated?
Pegasystems Inc.
US
Let me check into this before providing a definitive response. For now I can tell you that there were none listed at the time we posted this initial draft. It wasn't too long ago, and we do have a recurring action to do maintenance to ensure this list is up-to-date. Let me inquire into this further and if there are any new updates, I'll ensure they get documented and then reply back here.
Pegasystems Inc.
US
I've run the latest report for 7.x and the catalog I link to above is up-to-date. There are no critical hot fixes listed after 7.3 for the 7.x release.
ANZ
IN
Setting : <env name=”lac/traditionalLACRegisterSynch” value=”true” />
When we can get rid of this setting in future? Or the apps in these Pega versions need to live with that forever?
Thank you
Pegasystems Inc.
US
Hello Savvy one!
nice question. No, you won't have to keep this forever. When you upgrade to the next forthcoming patch release, you could then get rid of this setting. Changes have already been made in the 8.1.x & 8.2.x patch release streams so that the next patch releases of those that come out later this summer will make the traditional synchronization policy the default
Thanks
Pegasystems Inc.
US
Hello Niladri
How are you?
You only need to change one or the other. Both ways control the same setting. You can choose the one that best fits your deployment. If it's easier for you to change the config file, then do that. Or if it's easier to control command line args, then choose that route
Thanks
Ford Motor Company
US
Hello Niladari- We were suggested by one of Pega's performance tuning expert, to remove all the settings out of prconfig file and keep them as DSS's, if any JVM args required, add them at the JVM level.
We havebeen following that approach past one year and our applications running stable. I would suggest to go the same way.
Thanks!
Pegasystems Inc.
US
Hello Ranjithkumar
The problem can occur in 8.2.1. That's why this notice is being communicated.
Please take the appropriate action for your deployment.
Thanks
Cognizant
IN
There is an optimistic way to detect DEAD locks by using ThreadMXBean, which provides a method called findDeadLockthreads() which returns id of all those threads which are in deadlock and waiting for each other to release monitor or acquire lock.
ThreadMXBean threadMBean = ManagementFactory.getThreadMXBean();
threadMBean.findDeadlockedThreads();
And using this approach we can kill the DEAD locks by doing further optimization capability of System Cleaner agent to do above monitor and kill the dead locks to prevent from system failure.
Could you review this approach with Engineering Team ?
Regards
Bhagath
Certified J2EE / Pega CLSA
There is an optimistic way to detect DEAD locks by using ThreadMXBean, which provides a method called findDeadLockthreads() which returns id of all those threads which are in deadlock and waiting for each other to release monitor or acquire lock.
ThreadMXBean threadMBean = ManagementFactory.getThreadMXBean();
threadMBean.findDeadlockedThreads();
And using this approach we can kill the DEAD locks by doing further optimization capability of System Cleaner agent to do above monitor and kill the dead locks to prevent from system failure.
Could you review this approach with Engineering Team ?
Regards
Bhagath
Certified J2EE / Pega CLSA
Cognizant
IN
>>> EITHER <<<
prconfig.xml should have to following entry
<env name="lac/traditionalLACRegisterSynch" value="true"/>
>>> OR <<<
JVM argument should be set as
-DNodeSettings=lac/traditionalLACRegisterSynch=true
Pegasystems Inc.
US
Hello Rajani
How are you?
Yes, it's resolved in 8.1.6. it's been fixed in every patch release cycle for 8.1, 8.2, & 8.3
Thanks