Skip to content

ARTEMIS-6141 Fix non-portable kill -SIGINT#6558

Merged
gemmellr merged 1 commit into
apache:mainfrom
lavocatt:fix-sigint-kill-upstream
Jul 2, 2026
Merged

ARTEMIS-6141 Fix non-portable kill -SIGINT#6558
gemmellr merged 1 commit into
apache:mainfrom
lavocatt:fix-sigint-kill-upstream

Conversation

@lavocatt

@lavocatt lavocatt commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

LargeMessageInterruptTest.killProcess() relies on Runtime.exec("kill -SIGINT ...") to send a graceful shutdown signal. The -SIGINT flag is a non-standard signal specification that some kill implementations silently ignore while reporting success (exit code 0), causing the broker process to stay alive and the test to time out. Observed on Fedora 43 where /usr/bin/kill does not handle -SIGINT.

Replace with Process.destroy() which sends SIGTERM directly via JVM syscall, with no dependency on external binaries or their flag parsing behavior.

LargeMessageInterruptTest.killProcess() relies on Runtime.exec("kill -SIGINT ...")
to send a graceful shutdown signal. The -SIGINT flag is a non-standard signal
specification that some kill implementations silently ignore while reporting
success (exit code 0), causing the broker process to stay alive and the test
to time out. Observed on Fedora 43 where /usr/bin/kill does not handle -SIGINT.

Replace with Process.destroy() which sends SIGTERM directly via JVM syscall,
with no dependency on external binaries or their flag parsing behavior.

Assisted-by: Cursor
@lavocatt lavocatt force-pushed the fix-sigint-kill-upstream branch from c2619f9 to ce97e7f Compare July 2, 2026 11:05
@gemmellr gemmellr merged commit 9196610 into apache:main Jul 2, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants