Cancelling the Baseline Indexing Job from SimpleIndexingAdmin does not Release Update Lock and Warns "WARNING: Failed to obtain lock."
Last updated on JANUARY 05, 2017
Applies to:Oracle Commerce Platform - Version 10.1.1 and later
Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 3.1.0 and later
Information in this document applies to any platform.
Cancelling the indexing job during EndecaIndexing state (/atg/commerce/endeca/index/EndecaScriptService), the last script in the baseline index process does not release the update_lock. As a result, any subsequent baseline or partial updates fail with the message "WARNING: Failure to acquire lock." You will see the following warning in the application log (e.g. \<app>\logs\<app>.0.0.log).
This issue also occurs if subsequent CA deployment starts while an indexing job is still running.
1. Indexing is started, PreIndexing and RepositoryExport phases are successful and EndecaIndexing (/atg/commerce/endeca/index/EndecaScriptService) is still running.
2. CA deployment is run.
3. Indexing job in Step 1 gets cancelled and pushed into queue. (At this step update_lock on Endeca site is not released.)
4. CA Deployment in Step 2 complete.
5. Indexing from queue is re-run and fails with "WARNING: Failed to obtain lock".
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms