Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Derby Embedded DB stays open when using the Gradle wrapper #2088

Closed
timmyhadwen opened this issue Jul 17, 2018 · 1 comment
Closed

Derby Embedded DB stays open when using the Gradle wrapper #2088

timmyhadwen opened this issue Jul 17, 2018 · 1 comment

Comments

@timmyhadwen
Copy link

@timmyhadwen timmyhadwen commented Jul 17, 2018

Which version and edition of Flyway are you using?

flyway 5.1.4, Derby 10.14.2.0,

Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)

Gradle plugin

Which database are you using (type & version)?

Derby Embedded Client

Which operating system are you using?

MacOS 10.11 but also confirmed happening on Windows using bash.

What did you do?

(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
Running 'gradle flywayMigrate' twice causes derby database to not be connected due to the lock files still being valid. Running 'pkill java' fixes the issue for another run. 'gradle flywayMigrate --no-daemon' makes the issue go away.

@axelfontaine
Copy link
Contributor

@axelfontaine axelfontaine commented Aug 2, 2018

Good point. This has now been fixed.

axelfontaine added a commit to flyway/flywaydb.org that referenced this issue Aug 2, 2018
dohrayme pushed a commit to dohrayme/flyway that referenced this issue Feb 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.