forked from akhikhl/gretty
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Errors seem to leave gretty/jetty running without the ability to shutdown without killing processes manually #291
Comments
|
|
I confirm the issue with gretty 4.1.1 and gradle 8.0.1 and gradle 8.5 under macOS with openjdk 17.0.4.1 2022-08-12. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Whenever my app has either a runtime or build-time error it sees to leave jetty in a bad state where gretty doesn't shut it down automatically, or by using one of the stop commands. I have to manually kill the process in order to run it again, otherwise I get an error message about the port already being in use.
The text was updated successfully, but these errors were encountered: