当前位置:网站首页>Solve liquibase – waiting for changelog lock Cause database deadlock

Solve liquibase – waiting for changelog lock Cause database deadlock

2022-07-05 09:42:00 zch981964

  1. The cause may be idea Frequent operation , Lead to Jar Packet start error , Workflow table part log table is locked , The exception may be caused by the last abnormal termination of the program .
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....
  1. Learn from the Internet and say that the table is locked , Just unlock it , You can execute the following statement , But the prompt cannot find the table or the attempt does not exist
# Query the locked table 
SELECT * FROM DATABASECHANGELOGLOCK;
# Unlock 
UPDATE DATABASECHANGELOGLOCK SET locked=0, lockgranted=null, lockedby=null WHERE id=1
  1. terms of settlement ( All with DATABASECHANGELOGLOCK Check all the tables at the end , And modify it locked The value of the field is 0 that will do , Such as : chart 2
     Insert picture description here
    4、 Rerun the project , It shows that the operation is normal .
原网站

版权声明
本文为[zch981964]所创,转载请带上原文链接,感谢
https://yzsam.com/2022/186/202207050928255349.html