-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Quarkus Dev Mode Hangs on stop #33896
Comments
When the process hangs, use |
Thanks @gsmet . This is the output:
|
I can't really find anything that allows me to fix this. What I (think) I know so far:
Does anyone else that use podman get this ? |
After updating to Fedora 38 we have issues with Horreum (https://github.com/Hyperfoil/Horreum) test suite (Horreum is based on Quarkus using Keycloak). The test suite hangs and after I kill it I see two docker.io/testcontainers/ryuk:0.3.4 running and one docker.io/library/postgres:13 when using 'podman ps'. I think it's related to the hanging postgres process. When I do a 'podman kill -a' I can start the test suite again and it will run a few tests before hanging. If I do not kill the podman processes the first test will never start as it will wait for testcontaines to start. |
I am seeing similar issues with Quarkus 3.3.2 in OpenShift Dev Spaces / Eclipse Che. If I use a VS Code task to start live dev mode, it does not stop when I stop the task. I cannot restart dev mode at this point because the required ports are still bound by the previous process. If I start dev mode from a terminal, it requires two |
The above might have been self inflicted... I can no longer reproduce it. |
Describe the bug
I have this issue with the latest released (3.1.1) and main (999-SNAPSHOT) versions of Quarkus that I start an app in dev mode, then stop it (using ctl-c) but that does not stop quarkus and I have to do a kill -9 to stop the process. After killing the process, the app can not start up properly anymore and I have to restart my laptop to get it to start.
Now, this is probably just on my laptop and something weird with my environment, but I thought I'll log the bug and see if anyone can help me. It seems connected to the docker instance started by Testing (Keycloak in this case), but I'll investigate further. To recreate, create an app from code.quarkus.io with oidc, resteasy reactive and smallrye open api, start the app and then stop it.
I am using podman version 4.5.1
Expected behavior
The app stop and can be started again
Actual behavior
The app hangs on stop and needs to be killed
How to Reproduce?
code-with-quarkus(12).zip
Use above app, start it, go to dev ui, stop it, see if it hand for you.
Output of
uname -a
orver
Linux pkruger-laptop 6.3.5-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Tue May 30 15:44:17 UTC 2023 x86_64 GNU/Linux
Output of
java -version
openjdk version "17.0.7" 2023-04-18 OpenJDK Runtime Environment (Red_Hat-17.0.7.0.7-4.fc38) (build 17.0.7+7) OpenJDK 64-Bit Server VM (Red_Hat-17.0.7.0.7-4.fc38) (build 17.0.7+7, mixed mode, sharing)
GraalVM version (if different from Java)
No response
Quarkus version or git rev
3.1.1 or 999-SNAPSHOT
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.9.1 (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
Additional information
No response
The text was updated successfully, but these errors were encountered: