You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@artemis.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2026/07/02 11:24:00 UTC
[jira] [Commented] (ARTEMIS-6141) LargeMessageInterruptTest.killProcess() relies on non-portable kill -SIGINT flag
[ https://issues.apache.org/jira/browse/ARTEMIS-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18093219#comment-18093219 ]
ASF subversion and git services commented on ARTEMIS-6141:
----------------------------------------------------------
Commit 91966100c2884e7d26503bfe98b2b2d89dcda31c in artemis's branch refs/heads/main from Thomas Lavocat
[ https://gitbox.apache.org/repos/asf?p=artemis.git;h=91966100c2 ]
ARTEMIS-6141 Fix non-portable kill -SIGINT
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
> LargeMessageInterruptTest.killProcess() relies on non-portable kill -SIGINT flag
> --------------------------------------------------------------------------------
>
> Key: ARTEMIS-6141
> URL: https://issues.apache.org/jira/browse/ARTEMIS-6141
> Project: Artemis
> Issue Type: Bug
> Reporter: Thomas Lavocat
> Priority: Major
>
> LargeMessageInterruptTest.killProcess() uses Runtime.getRuntime().exec("kill -SIGINT " + process.pid()) to send a graceful shutdown signal to the broker process.
> The -SIGINT flag is a non-standard signal specification. On some systems (e.g. Fedora 43), the kill binary does not recognize -SIGINT — it silently exits with code 0 but never delivers the signal. The broker process stays alive, waitFor(1, MINUTES) times out, and the test fails.
> The behavior depends on which kill implementation is present on the system:
> Some accept -SIGINT (stripping the SIG prefix internally)
> Some reject it as an invalid signal specification
> Some silently ignore it while reporting success (exit code 0)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org