Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Frequent RequestorLockException and hung threads in multi node

SA-1897

Summary



Hung threads were reported very frequently in the PRPC 6.1 SP2 environment after it was recently moved to WebSphere v7.0.0.31. PRPC application works properly after restart for few hours and threads start getting hung again. Same application was working properly in their old environment which was based on WebSphere v6.  

Error Messages



com.pega.pegarules.pub.context.RequestorLockException: Unable to synchronize on requestor H2BE70F82F71B384A785A1F81C2725E47 within 120 seconds and also some of assembly related errors.

Steps to Reproduce



NA

Root Cause



User have two PRPC nodes (two JVMs connecting to same PegaRULES database) and both were pointing to same PRPC temporary directory. Such misconfiguration would cause frequent requestor lock and assembly related issues.

Resolution



Each PRPC node must have its separate PRPC temporary directory. With this configuration change, reported issues were resolved.

Published January 31, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us