Sunday, March 20, 2016

Oracle Endeca 10.x : Cancelling the Baseline from SimpleIndexingAdmin does not Release Update Lock

Cancelling the indexing job during EndecaIndexing state (/atg/commerce/endeca/index/EndecaScriptService), the last script in the baseline in... thumbnail 1 summary
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." Following warning in the application log can be seen below:-


Aug 9, 2015 5:16:54 PM com.endeca.soleng.eac.toolkit.Controller setUpBeanShellInterpreters
CONFIG: Loading beanshell.imports from /<some path>/<app>/config/script/beanshell.imports
Aug 9, 2015 5:16:54 PM com.endeca.soleng.eac.toolkit.Controller provision
INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
Aug 9, 2015 5:16:54 PM com.endeca.soleng.eac.toolkit.Controller provision
INFO: Definition has not changed.
Aug 9, 2015 5:16:54 PM sun.reflect.NativeMethodAccessorImpl invoke0
INFO: Starting partial update script.
Aug 9, 2015 5:16:58 PM sun.reflect.NativeMethodAccessorImpl invoke0
WARNING: Failed to obtain lock.

Note: - This issue also occurs if subsequent BCC deployment starts while an indexing job is still running.

Workaround

Under <endeca_app_path>/control on Endeca side, run the runcommand to release lock.
/runcommand.sh" --skip-definition LockManager releaseLock update_lock

Solution

Hot patch has been released from Oracle on this.

Hotfix Patch 17298595

No comments

Post a Comment

Text Widget