Upgrade Hsqldb to version that doesn't cause Flyway to deadlock
See original GitHub issueWhen I upgrade my projects to use Spring Boot 1.3.6 instead of 1.3.5 my flyway migration test gets stuck. Here’s a very minimal sample project: https://github.com/timtebeek/flyway-hsqldb
Setting spring-boot-starter-parent
to 1.3.5.RELEASE
will make the test succeed. With 1.3.6.RELEASE
it gets stuck, as shown here: https://travis-ci.org/timtebeek/flyway-hsqldb/builds/144749071
Can anyone look into it and confirm/fix my issue? (And is this the right place?)
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (9 by maintainers)
Top Results From Across the Web
Migration hanging with HsqlDB 2.3.4 · Issue #1346 - GitHub
I was using flyway 4.0 with hsqldb driver 2.3.3 for the last couple months. I start up my server, start my process which...
Read more >Release Notes - Flyway by Redgate • Database Migrations ...
SQL*Plus 'spool' now ignores value of 'feedback' for update statements; Issue 3413 Script migrations applied previously using Teams Edition no longer cause ......
Read more >1441 Deadlock when using HyperSQL 2.3.4 with Flyway ...
The lock behaviour has been enhanced for the next versions 2.3.5 / 2.4.0 and committed. It will allow the Flyway migration to work,...
Read more >hsqldb hibernate persist @Lob - java - Stack Overflow
I have migrated to 2.3.1, got error in a same place, but with more specific explanation: HsqlException: data exception: string data, ...
Read more >ErrorCode - H2 Database Engine
The error with code 90131 is thrown when using multi version concurrency control, and trying to update the same row from within two...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @timtebeek ,
This seems to have to do with the version of HSQLDB.
In Spring Boot 1.3.5 the version was 2.3.3 and in Spring Boot 1.3.6 the version is 2.3.4.
If you manually downgrade just your HSQLDB version you will see your test succeed.
The following Stackoverflow question led me to this information and may have more information to help you solve this. Stackoverflow Question
Closed by 5291fb5ff703e282ab8a8fa82d0757c83e4a0fd2