Support Article

Rule Search Index does not finish

SA-29107

Summary



User went to the menu option User System > Settings > Search landing page and started the indexing.

Although the process completed for Work  and Data instances, it stopped for Rules at around 65,000 records.

The search landing page and PegaRULES log file have no error reported.


Error Messages



Not applicable


Steps to Reproduce

  1. Go to Search Landing page.
  2. Select Rules Reindex.


Root Cause



A defect in Pegasystems’ code or rules.

The indexing process adds rows to 
pr_log_cluster table as instances of Log-Cluster-FTSIndex when an error is encountered while indexing.

These entries from the time when issue was reported reveal that indexing is failing due to "caught exception during autocommit check" error. This error occurs when Pega returns a database Connection back to the jdbc connection pool once the current request processing is complete.

Pega checks if auto commit is marked to the appropriate value before returning the connection back to the pool. This error occurs when it gets the auto commit value on a closed connection.


Resolution



Perform the following steps:
  1. Apply Hfix-29715.​
  2. Restart JVM for the engine code change to take effect. The code now handles the Connection Closed Exception and removes the bad connection from the pool when appropriate.

Published October 12, 2016 - Updated October 20, 2016

Have a question? Get answers now.

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