Discussion

21
Replies
3974
Views
BrendanHoran_GCS Member since 2011 78 posts
MOD
Posted: 1 year ago
Last activity: 10 months 3 weeks ago

Pega Proactive Notice: Thread Locking

Environments on the following Pega 8.X releases may possibly experience an issue with user or batch sessions becoming blocked or unresponsive:
  • 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
All subsequent Pega 8.X releases include mitigation to this potential issue.
How to avoid the issue
To ensure relevant environments do not incur the thread locking issue, it is recommended that all environments proactively enable a defined configuration setting.
This setting must be configured via prconfig.xml or a JVM command line argument. It cannot be set via a Dynamic System Setting.
Steps to Take
To avoid this issue using a prconfig.xml setting follow the steps described in the Modifying the prconfig.xml file Designer Studio Help article to add the below setting to every Pega node/JVM in the cluster:
<env name=”lac/traditionalLACRegisterSynch” value=”true” />
To avoid this issue through a generic JVM argument add the below string to every Pega node/JVM in the cluster. How to add generic JVM arguments varies between application servers and your environment setup. Contact Pega GCS if you need help.
-DNodeSettings="lac/traditionalLACRegisterSynch=true"
*IMPORTANT* After implementing the change, an accompanying node restart must be initiated.
Get help
If you encounter issues implementing the prconfig change or have questions about it, post your questions below. The Global Client Support engineers in the PSC will answer your questions or determine and advise if you need to go to My Support Portal to submit a Support Request (SR).
System Administration
Share this page LinkedIn