I'm testing a minimal Quarkus application (a Java framework) on the very latest previews of OpenJDK 23.
When running in a shell on Fedora Linux 40, it starts fine and terminates correctly when I hit Ctrl+C (Sending SIGINT).
The same application, when running in a container based on the same Fedora 40 version, when sending SIGINT it also terminates correctly - but only when running on OpenJDK 22.
When running the same application on a freshly built preview of OpenJDK 23, SIGINT is handled correctly when running from a local shell but the signal seems ignored when running the same app within a container.
Having noticed https://bugs.openjdk.org/browse/JDK-8309155, I've experimented with -Djdk.console=java.basebroken : setting this property works around the problem and has the JVM terminate correctly.
I have to admit my "faulty" OpenJDK 23 is a custom local build; I can try to verify this with an official preview tag but having narrowed it down to being related toJDK-8309155 perhaps that's unnecessary?
When running in a shell on Fedora Linux 40, it starts fine and terminates correctly when I hit Ctrl+C (Sending SIGINT).
The same application, when running in a container based on the same Fedora 40 version, when sending SIGINT it also terminates correctly - but only when running on OpenJDK 22.
When running the same application on a freshly built preview of OpenJDK 23, SIGINT is handled correctly when running from a local shell but the signal seems ignored when running the same app within a container.
Having noticed https://bugs.openjdk.org/browse/JDK-8309155, I've experimented with -Djdk.console=java.basebroken : setting this property works around the problem and has the JVM terminate correctly.
I have to admit my "faulty" OpenJDK 23 is a custom local build; I can try to verify this with an official preview tag but having narrowed it down to being related to
- duplicates
-
JDK-8332921 Ctrl+C does not call shutdown hooks after JLine upgrade
-
- Resolved
-