Wednesday, July 6, 2016

milliseconds on entry key=atg.repository.search.indexing.ConfigStatePersister.ClaimedLock

While I was doing startup on my localenvironment I found an exception this exception:

milliseconds on entry key=atg.repository.search.indexing.ConfigStatePersister.ClaimedLocknull

I did not find a solution on the internet, but lucky for me oracle have a solution for this on the Oracle Knowlage base.

The root cause seems to be an unexpected stop or kill of the current application leaving the locks alive in Server Lock Manager, since this was on my local environment the solution was easy for me.

just do: 

useLockServer=false

on my ClientLockManager components.

The solution for non development instances is shoutdown the LockManager server, so it release the locks

Post a Comment