OK, I'm stuck. Our primary instance works (with supportSequence() returning false), but I can't get rid of the DATABASECHANGELOGLOCK thing. I've tried to debug a bit into the liquibase coding, but I'm getting lost there.
Scenario: We have two web applications running on a single Tomcat. The first web application has the LiquibaseServletListener configured to keep our DB schema up-to-date. This first web application works fine. The second web application has a javax.sql.DataSource as reference in it's web.xml and call Liquibase programmatically. Both web applications use the same liquibase version, but for some reason the second web app tries to recreate the DATBASECHANGELOGLOCK table when it's called.
Any ideas?
Thanks and best regards,
Marc