Flyway migration fails with the latest MSSQL RHEL server (most often on RHEL) #46083
Comments
michalvavrik
added
area/flyway
kind/bug-thirdparty
|
/cc @cristhiank (flyway), @gastaldi (flyway), @geoand (flyway), @gsmet (flyway) |
|
@michalvavrik there was an idea that the failure was reproducible on JDK 17 and not on 21. Was that confirmed or JDK version doesn't have any effect? |
I never said anything like that, I tried every possible combination, it is not related to JDK version. |
|
Maybe @jcarranzan mentioned JDK version? anyway, not related. |
|
I found it, you are referring to passing JDK 21 Job, I tried it and reproduced it with 21. I think there is a race somewhere and even a little things can influence that. But the reproducer I provider is stable, because I only failed to reproduce it once in many runs. I tried it from scratch with new instances more than once. |
|
I rerun that job created by @jcarranzan and it failed with 21 as well. Sending you link via DM. |
|
When I tested last week, this failed for openJDK17 and passed with openJDK21, that's what I said. But probably as @michalvavrik mentioned, it is possible that it was a race issue and it confused me... |
|
Thanks Michal for the thorough checks and confirmation it's not JDK related. |
|
Updated reproducer, now failure also happens sometimes in GH CI, so it is combination of Ubuntu and RHEL9 |
michalvavrik
changed the title
|
TBH, I'm not sure we can do anything about this on the Quarkus side. |
I expected that, I just needed to check. Once you are certain, please close this issue. Thanks |
Describe the bug
I presume this will get closed, but I can't with a good conscience decide for myself that this is 100 % not related to Quarkus. I experience bug only on RHEL8, when the same thing is executed on RHEL9 or Fedora, all is working. Very rarely I can't reproduce it on RHEL8, so maybe it is little flaky, but almost always it fails. And it doesn't happen with non-RHEL SQL server.
TL;DR; migration fails with "connection closed" and I am not sure if it is not related to Agroal or if it is only Flyway & MSSQL issue.
Expected behavior
Migration pass.
Actual behavior
Application fails to start and exception is thrown:
How to Reproduce?
Steps to reproduce the behavior:
There are other ways to reproduce this, for example you can run Quarkus QE Test Suite vertx-sql module https://github.com/quarkus-qe/quarkus-test-suite/actions/runs/13191616175/job/36825489234.
Output of
uname -aorverRed Hat Enterprise Linux release 8.10 (Ootpa)
Output of
java -versionOpenJDK Runtime Environment (Red_Hat-17.0.12.0.7-1) (build 17.0.12+7-LTS)
Quarkus version or git rev
3.15,3.18,999-SNAPSHOT (in short: all I tried)
Build tool (ie. output of
mvnw --versionorgradlew --version)Apache Maven 3.9.9
Additional information
Docker container image:
mcr.microsoft.com/mssql/rhel/server@sha256:af5b907277cbe8f82a8986d7abd5c954459cbc77a0358ad0eab80471b53e311bWorks with older RHEL-based SQL Server images like
http://mcr.microsoft.com/mssql/rhel/server:2022-CU10-rhel-9.1Feel free to close the issue.
The text was updated successfully, but these errors were encountered: