You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@artemis.apache.org by "Domenico Francesco Bruscino (Jira)" <ji...@apache.org> on 2026/08/21 11:16:00 UTC
[jira] [Closed] (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:all-tabpanel ]
Domenico Francesco Bruscino closed ARTEMIS-6141.
------------------------------------------------
> 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: Task
> Reporter: Thomas Lavocat
> Priority: Major
> Fix For: 2.56.0
>
>
> 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