Production system is getting crashed quite often.
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.
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
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:
After reviving the .dat file from the server, and increasing the RAM, system becomes stable.
0% found this useful