(RPA) Support Tip: Starting Central hangs with "Waiting for changelog lock"

0 Likes

When starting RPA Central, entries in the wrapper log are seen,

SEVERE: Exception sending context initialized event to listener instance of class [com.hp.oo.webapp.listeners.OoLiquibaseServletListener]
java.lang.RuntimeException: liquibase.exception.LockException: Could not acquire change log lock. Currentlylocked by (this central server) since x/xx/xxxx 15:34
               at liquibase.integration.servlet.liquibaseServletListener.contextInitialized(liquibaseServletListener,java:123)
               at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4678)
               …..
Caused by: liquibase.exception.LockException: Could not acquire change log lock. Currently locked by .......
               at liquibase.lockservice.StandardLockService.waitforlock(StandardLockService.java:174)

This error could occur if the application does not stop correctly (service stop) but it stops incidentally (such as force shutting down). 

Run “Select * from DATABASECHANGELOGLOCK” against RPA central DB. If “Locked” column “1” is seen, and ”LOCKGRANT” and “LOCKEDBY” are not “null”. The error will be thrown.

1. Stop central service,
2. Run RPA/Central/bin/release-log-lock.bat. It will reset “Locked” to “0”, ”LOCKGRANT” to “null” and “LOCKEDBY” to “null”.
3. Start central service.

Labels:

Support Tip
Comment List
Related
Recommended