You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When liquibase.datasources.default.async is true, migrations often (but not always) fail. Usually with an error referencing locks or a failure to transition to a state when another is still open. Something like:
Caused by: java.lang.RuntimeException: Cannot end scope omefbvcocj when currently at scope cnlydevtnl
TBH I think introducing the async migrations wasn't a good idea. I haven't seen this error before until I've tried to upgrade to Liquibase 4.4.x. Now a couple of tests fail (sometimes) with that error.
I have the same problem using Micronaut v3.1.4. I need liquibase to run asynchronously because multirow inserts for lots of test data (divided into manageable changeset batches) take a long time to run and the microservice should be up and running quite a bit sooner
When
liquibase.datasources.default.async
istrue
, migrations often (but not always) fail. Usually with an error referencing locks or a failure to transition to a state when another is still open. Something like:For an example app, please see: https://github.com/JasonTypesCodes/mn-liquibase-259
Starting the app with
./gradlew run
will likely illustrate the error. If your changeliquibase.datasources.default.async
tofalse
, the issues go away.Environment Information
Example Application
https://github.com/JasonTypesCodes/mn-liquibase-259
The text was updated successfully, but these errors were encountered: