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

Incorrect email sent by NBAM when Segment refresh fails

SA-1176

Summary



User had reported a failure in the scheduled NBAM Segment refresh process. Log files depicte that there were various Locking exception on the Indexer Agent due to which the "RefreshBaseSegment" Segment rule could not auto-refresh. This behavior was resolved after removing the ".lock" file from the temp directory and a server restart.

User has raised concerns around NBAM not sending correct e-mail with the exception details when such issues occur during Segment Refresh.


Error Messages



2014-05-04 11:17:22,385 [ PegaRULES-Batch-4] [ STANDARD] [ PegaNBAM:06.03] ( search.internal.RuleIndexer) ERROR - Failed to update ClipboardPages in the PegaRULES index- Lock obtain timed out: [email protected]/smartpaas-app/tomcat/node1/PegaRULESIndex/DataIndex/write.lock
2014-05-04 11:17:22,386 [ PegaRULES-Batch-4] [ STANDARD] [ PegaNBAM:06.03] ( SystemIndexer.Code_.Action) ERROR - [ Indexer ] The System Indexer encountered an error
com.pega.pegarules.pub.PRRuntimeException: Failed to update the PegaRULES index - Lock obtain timed out: [email protected]/smartpaas-app/tomcat/node1/PegaRULESIndex/DataIndex/write.lock
at com.pega.pegarules.search.internal.RuleIndexer.updateIndex(RuleIndexer.java:1385)

 
Caused by: com.pega.apache.lucene.store.LockObtainFailedException: Lock obtain timed out: [email protected]/smartpaas-app/tomcat/node1/PegaRULESIndex/DataIndex/write.lock
at com.pega.apache.lucene.store.Lock.obtain(Lock.java:85)
at com.pega.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:1108)


Steps to Reproduce



Schedule a Segment to auto run and make sure a failure was induced during Segment execution.

Root Cause



Even in case of a failure of the scheduled Segment execution, NBAM sends out an email with a success message and it does not include the error message causing the Segment refresh failure.

Resolution



HFix-9661 was provided to address this issue. With this HFix, NBAM sends out the error message in the e-mail when the Segment refresh fails.
 

Published January 31, 2016 - Updated December 2, 2021

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