Liquibase exception

Support
#1

I am having the following exception when trying to run the application. it was running well but starting this when I added more tables… I am a kind of puzzled as I hardly get such exceptions in CUBA-PLATFORM for a database update, is there something to do with the Liquibase?

Caused by: org.springframework.beans.factory.BeanCreationException at AbstractAutowireCapableBeanFactory.java:1804

[2022-03-21 20:24:47] INFO [liquibase.changelog] Reading resource: com/inteacc/pf/liquibase/changelog/2022/03/21-120-b5c068c4.xml
[2022-03-21 20:24:49] INFO [liquibase.changelog] Reading from PUBLIC.DATABASECHANGELOG
[2022-03-21 20:24:49] INFO [liquibase.lockservice] Successfully released change log lock
20:24:49.837 [main] INFO hsqldb.db.HSQLDB7CD998E83E.ENGINE - Database closed
Unexpected error running Liquibase: Validation Failed:
     3 change sets check sum
          com/inteacc/pf/liquibase/changelog/2022/03/21-120-b5c068c4.xml::1::pf was: 8:139780d64c662f266a8d91a6bd72bfd6 but is now: 8:e1b53b890bfcad8f65f5c22d20508862
          com/inteacc/pf/liquibase/changelog/2022/03/21-120-b5c068c4.xml::2::pf was: 8:5fb3dca6ad6e32040419f20e95bc4d66 but is now: 8:53a3372439e72ff54dd6f085dbfb1c5a
          com/inteacc/pf/liquibase/changelog/2022/03/21-120-b5c068c4.xml::3::pf was: 8:beb01026785a544b6d12892bdd2b9745 but is now: 8:e2618117ffed253824370e673fa75362

For more information, please use the --logLevel flag
[2022-03-21 20:24:49] SEVERE [liquibase.integration] Unexpected error running Liquibase: Validation Failed:
     3 change sets check sum
          com/inteacc/pf/liquibase/changelog/2022/03/21-120-b5c068c4.xml::1::pf was: 8:139780d64c662f266a8d91a6bd72bfd6 but is now: 8:e1b53b890bfcad8f65f5c22d20508862
          com/inteacc/pf/liquibase/changelog/2022/03/21-120-b5c068c4.xml::2::pf was: 8:5fb3dca6ad6e32040419f20e95bc4d66 but is now: 8:53a3372439e72ff54dd6f085dbfb1c5a
          com/inteacc/pf/liquibase/changelog/2022/03/21-120-b5c068c4.xml::3::pf was: 8:beb01026785a544b6d12892bdd2b9745 but is now: 8:e2618117ffed253824370e673fa75362

liquibase.exception.ValidationFailedException: Validation Failed:
     3 change sets check sum
          com/inteacc/pf/liquibase/changelog/2022/03/21-120-b5c068c4.xml::1::pf was: 8:139780d64c662f266a8d91a6bd72bfd6 but is now: 8:e1b53b890bfcad8f65f5c22d20508862
          com/inteacc/pf/liquibase/changelog/2022/03/21-120-b5c068c4.xml::2::pf was: 8:5fb3dca6ad6e32040419f20e95bc4d66 but is now: 8:53a3372439e72ff54dd6f085dbfb1c5a
          com/inteacc/pf/liquibase/changelog/2022/03/21-120-b5c068c4.xml::3::pf was: 8:beb01026785a544b6d12892bdd2b9745 but is now: 8:e2618117ffed253824370e673fa75362

	at liquibase.changelog.DatabaseChangeLog.validate(DatabaseChangeLog.java:299)
	at liquibase.Liquibase.lambda$update$1(Liquibase.java:231)
	at liquibase.Scope.lambda$child$0(Scope.java:177)

Note: I am using the latest version of studio and platform released recently.

#2

What database are you using?
If MySQL, this issue can be the cause: https://youtrack.jmix.io/issue/JST-2673

#3

Hi Konstantin
Since this is a new project, I didn’t use any modern database yet but using hsqldb by default (it will run on SQL server). Do you recommend I should switch to SQL server sooner than later to avoid such problems?

#4

Hi Mortoza
HSQL itself could not be the cause. The only reason for such errors is that your Liquibase changelog files were modified after they were run against the database. Make sure you don’t do it manually. If you can trace a scenario when it’s done by Studio, please let us know.

#5

Hi Konstantin
I didn’t change anything related. Ok, will send you if it happens again.