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

Production system is getting crashed quite often.

SA-20314

Summary



Primary node on production is getting crashed. It has been observed in System Management Application (SMA) that number of batch requestors for PEGARULES are getting accumulated, and the free memory is getting lesser. The following error can be observed in the log file.


Error Messages



2016-02-09 00:00:21,744 [fault (self-tuning)'] [ STANDARD] [ PegaRULES:06.03] ( search.internal.RuleIndexer) ERROR - Failed to update ClipboardPages in the PegaRULES index - Lock obtain timed out:
2016-02-09 00:00:21,745 [fault (self-tuning)'] [ STANDARD] [ PegaRULES:06.03] (xer.System_Work_Indexer.Action) ERROR - [ Indexer ] The System Indexer encountered an error
com.pega.pegarules.pub.PRRuntimeException: Failed to update the PegaRULES index - Lock obtain timed out: NativeFSLock@/var/SP/weloadm/pega/pegatempdir/PegaRULESIndex/DataIndex/write.lock



Steps to Reproduce



Not Applicable.

Root Cause



An issue in the custom application code or rules. The memory set was very low. .Dat file got created in the server at below location:

/var/SP/weloadm/admin/BPA_UAT/servers/managed2/data/store/default 

Resolution



After reviving the .dat file from the server, and increasing the RAM, system becomes stable.
 

Published May 14, 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