How to fix the "Failed to get a lock" error in Endeca?

Question

Endeka doesn't seem to be very popular, anyway

Problem:

Accidentally kill the current baseline update process, and the lock is left somewhere.

I want to find out where the lock is on the left, and manually remove this.

Not very useful message returned by updating the baseline script:

  INFO: Checking definition from AppConfig.xml against existing EAC provisioning.
 INFO: Definition has not changed.
 INFO: Starting baseline update script.
 WARNING: Failed to obtain lock.

 ... ended 

Alternatively, anyone can provide some links to endeca documentation (without login credentials).

Answer 1

RTFM

If the launched script deployment template breaks halfway through its execution due to an unhandled exception or is manually interrupted by the user by pressing Ctrl-C while it is running, the lock remains set in EAC.

On Windows:. .\runcommand.bat LockManager releaseLock update_lock

On UNIX: ./runcommand.sh LockManager releaseLock update_lock

Both of the above will work if the default lock name does not change (update_lock)

Answer 2

Assuming you are using your deployment template, I save the .bat file in the "control" directory when it comes in handy sometimes.

eg. on a Windows computer, create a .bat file with its contents:

 rem runcommand.bat/sh LockManager releaseLock update_lock call %~dp0..\config\script\set_environment.bat call %~dp0runcommand.bat LockManager releaseLock update_lock 

As for their documentation ... you need to register on your support site. I have not seen him anywhere else.

Answer 3

For an ATG application (or "Oracle Web Commerce") integrated with Endeca, this situation can occur when the work with the base index is canceled using the "Cancel" button in the graphical interface of the ProductCatalogSimpleIndexingAdmin component in Dyn Admin. Subsequent baseline updates will not work until a manual action is taken on the Endeca side to release the lock.

(I saw this with ATG 10.1.2 integrated with Endeca 3.1.1.)

In a conversation that I had with Oracle support, this is considered an error - "BUG 17298595 - Canceling the baseline from SimpleIndexingAdmin does not release the update lock" - and an ATG fix is ​​available.

Answer 4

Run the release_update_locks.sh (or .bat in case of windows) script from the application’s control folder.