1. Abnormal
Workflow module jar package startup error:
2021-02-14 13:45:13.735 [main] INFO liquibase - Waiting for changelog lock.... 2021-02-14 13:45:23.739 [main] INFO liquibase - Waiting for changelog lock.... 2021-02-14 13:45:33.744 [main] INFO liquibase - Waiting for changelog lock.... 2021-02-14 13:45:43.750 [main] INFO liquibase - Waiting for changelog lock.... 2021-02-14 13:45:53.755 [main] INFO liquibase - Waiting for changelog lock.... 2021-02-14 13:46:03.762 [main] INFO liquibase - Waiting for changelog lock.... 2021-02-14 13:46:13.767 [main] INFO liquibase - Waiting for changelog lock.... 2021-02-14 13:46:23.773 [main] INFO liquibase - Waiting for changelog lock....
2. Reasons
Some log tables of the workflow table are locked, which may be caused by the exception that the program was not terminated normally last time.
3. Learn from the online saying that the table is locked. Just unlock it. You can execute the following statement, but you will be prompted that the table cannot be found or does not exist
#Check the locked sheet SELECT * FROM DATABASECHANGELOGLOCK; #Unlock UPDATE DATABASECHANGELOGLOCK SET locked=0, lockgranted=null, lockedby=null WHERE id=1
4. Solution (check all tables ending with databasechangelock, and modify as shown in Figure 2)
Figure 1
Figure 2
Similar Posts:
- [Solved] MYSQL Deadlock found when trying to get lock; try restarting transaction
- SQL Error: Table is specified twice, both as a target for ‘UPDATE’ and as a separate source for data
- MySQL reports an error lock wait timeout exceeded; Try restarting transaction problem solving method
- How to Solve ra-28000 account being locked Error
- An error is reported when the SVN is submitted. The prompt is locked and cleanup is required
- [Solved] Git Error: “Another git process seems to be running in this repository…”
- Analysis of Android sleep wake mechanism — wake_ lock
- Another app is currently holding the yum lock; waiting for it to exit…
- MySQL Error: Waiting for table metadata lock [How to Solve]
- Svn is already locked